Need to remove compliance security profile from Databricks workspace

Devin Robbins - Thanks for the question and using MS Q&A platform.

You cannot remove the compliance security profile once it's been enabled on a Databricks workspace, as the change is permanent. The only way to get a workspace without the profile is to delete the existing one and create a new workspace without enabling the compliance security profile.

For more details, refer to Configure enhanced security and compliance settings.

Hope this helps. Let me know if you have any further questions or need additional assistance. Also, if these answers your query, do click the "Upvote" and click "Accept the answer" of which might be beneficial to other community members reading this thread.

𝘛𝘰 𝘴𝘵𝘢𝘺 𝘪𝘯𝘧𝘰𝘳𝘮𝘦𝘥 𝘢𝘣𝘰𝘶𝘵 𝘵𝘩𝘦 𝘭𝘢𝘵𝘦𝘴𝘵 𝘶𝘱𝘥𝘢𝘵𝘦𝘴 𝘢𝘯𝘥 𝘪𝘯𝘴𝘪𝘨𝘩𝘵𝘴 𝘰𝘯 𝘈𝘻𝘶𝘳𝘦 𝘋𝘢𝘵𝘢𝘣𝘳𝘪𝘤𝘬𝘴, 𝘥𝘢𝘵𝘢 𝘦𝘯𝘨𝘪𝘯𝘦𝘦𝘳𝘪𝘯𝘨, 𝘢𝘯𝘥 Data & AI 𝘪𝘯𝘯𝘰𝘷𝘢𝘵𝘪𝘰𝘯𝘴, 𝘧𝘰𝘭𝘭𝘰𝘸 𝘮𝘦 𝘰𝘯 𝘓𝘪𝘯𝘬𝘦𝘥𝘐𝘯.

Hi Devin Robbins,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

There isn’t a self-service way to “turn off” the Databricks Compliance Security Profile (CSP). It’s designed to be permanent. If a workspace has ever processed regulated data, the supported path is to create a new workspace without CSP.

What you can do now:

• Fastest workaround: create a new (Premium) workspace without CSP, attach it to the same Unity Catalog metastore, then re-create clusters, jobs, and notebooks. Use the shield icon in the UI to confirm which workspace has CSP.
• If you’re confident the workspace never handled regulated data, open an Azure Databricks support ticket and ask if they can assist. There’s no toggle in product;
• Expect side effects: enabling CSP also turns on the Enhanced Security & Compliance add-on billing and tightens defaults, which can impact AgentBricks and some AI/assist features.

Quick migration checklist:

• Back up notebooks (git or export), list jobs/schedules, and capture cluster policies.
• Create the new workspace without CSP; point to the same UC metastore (or set up a new one if desired).
• Recreate storage credentials/external locations, cluster policies, clusters, and jobs.
• Smoke-test jobs/permissions, then decommission the old workspace.

I hope this information is helpful! If you still have questions, please let us know what is needed in the comments so the question can be answered.