Block unmanaged customizations
What is unmanaged customizations?
Unmanaged customizations reside at the top layer for a component and subsequently define the runtime behavior of the component. Unmanaged customizations are typically applied directly to the environment where they are created. However, they can also be exported and imported as part of solutions, allowing you to transfer them between different environments
Block unmanaged customizations, what does it mean?
This environment setting allows system administrators to prevent unmanaged customizations in Microsoft Dataverse environments. By restricting unmanaged customizations, you guarantee that modifications to the environment originate solely from authorized application lifecycle management (ALM) procedures, ensuring adequate safety, transparency, and auditability.
This feature can be enabled or disabled from the Features area of the environment settings for environments in the Power Platform admin center. By default, this setting is disabled.

Please note that this feature is still in preview and therefore is not meant for production use.
What is blocked?
When the setting is enabled, these operations are blocked for the environment:
- Import of unmanaged solutions into the environment are blocked
- Creation of new solution components like apps, tables, and forms are blocked
- Adding unmanaged changes to existing managed components are blocked
- Any unmanaged changes result in an error returned to the user, such as: “This environment doesn't allow unmanaged customizations. This was a choice made by your admin, and certain actions won't be available or will be view only.”
What is NOT blocked?
- Change of environment variable, enabling or disabling components. For example, turning Power Automate flows on or off, assigning ownership, or sharing of table records.
- Solutions operations like remove Remove an unmanaged layer
- Creation and export of unmanaged solutions
Published on:
Learn moreWe can help you with Block unmanaged customizations
If you want help implementing, troubleshooting, or improving this product, contact us and we’ll point you in the right direction.
Related posts
Unmanaged developer environments are ending: what to do before December 15
Unmanaged developer environments can no longer be created, are suspended on December 15, 2026 and deleted in January. Who is affected and how ...
Backfill Dataverse prompt columns on existing records
Prompt columns only ran on new or updated rows. A bulk option now fills existing records as a system job: the two settings, the steps and the ...
Reveal a masked Dataverse column with Dataverse.Unmask
A new Power Fx function lets authorised users of a canvas app reveal one masked Dataverse value on demand, while column security stays in char...
Generative pages in model-driven apps: a practical guide
What generative pages are, where they stand in November 2026, the two ways to build them, the code they produce, and the limits to plan for.
Big Update — CRMJetty Dynamics 365 Portal Now Comes with Powerful New Integrations
Enterprise portals are evolving rapidly. They are no longer mere portals through which CRM records can be viewed. Portals are now expected to ...
Power Apps Code Apps in Practice: Recreating Model-Driven App Patterns
Power Apps Code Apps went from preview to general availability in record time. With that, Microsoft has sent a clear signal that it is taking ...
Use XRM type definition in your Javascript file
We implement Javascript webresource for form scripting (form onload, field on change,...). Our code need to follow the official document Xrm o...
Dataverse Functions Deep Dive
Microsoft released in 2024 Dataverse low-code plugins. The promise was great : writing plugins using low-code tools. No need to have developme...