web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Customer experience | Sales, Customer Insights,... / What are the potential...
Customer experience | Sales, Customer Insights,...
Answered

What are the potential issues with Managed environments

(3) ShareShare
ReportReport
Posted on by Samantha73 3,297
Hi All
I have 3 environments, dev, test, prod and I want to convert test and prod to Managed . What are the issues or considerations ? Or negatives related a managed environment vs unmanaged? Below are the licenses
Categories:
Microsoft Dynamics CRM
Dynamics 365 Sales
I have the same question (0)
  • Verified answer
    Quartzite Profile Picture
    Quartzite 135 on at

    Hi,

    No Direct Customization: Once deployed, any modifications must go through the development team, requiring an update and redeployment in production as a managed solution.

    Complex Removal Process: Removing a solution can be challenging, especially when dependencies exist.

    Rollback & Dependency Risks: Rolling back or removing a solution is difficult and may lead to broken dependencies, potentially impacting system stability.

     

    If you find this information helpful, please consider accepting it as the answer. 😊

  • Suggested answer
    Holly Huffman Profile Picture
    Holly Huffman 6,554 Super User 2026 Season 1 on at
    Hi there! Good morning, evening, or afternoon - depending on where you are :) Hope you are well today! 
     
    Converting your test and production environments to Managed in Microsoft Dynamics 365 has several considerations, both positive and negative.

    Key Considerations for Managed Environments
    1. Governance and Control:
      • Managed environments provide enhanced governance, allowing administrators to enforce policies, monitor usage, and maintain compliance.
      • This is particularly useful in production environments where stability and security are critical.
    2. Solution Management:
      • Managed solutions are locked, meaning components cannot be directly modified. This protects intellectual property and ensures consistency.
      • However, any changes require updates to the original unmanaged solution and re-importing, which can slow down the process.
    3. Layering and Dependencies:
      • Managed solutions support layering, allowing multiple solutions to coexist without conflicts.
      • Be cautious of dependencies between solutions, as removing a managed solution can sometimes lead to issues if other solutions rely on it.
    4. Flexibility:
      • Unmanaged environments offer greater flexibility for development and testing, as components can be modified directly.
      • Converting test to Managed may limit your ability to experiment and troubleshoot freely.
    5. Licensing:
      • Ensure your licenses align with Managed Environments' requirements. For example, Managed Environments are included with certain Dynamics 365 licenses. Based on your license list, you seem to have sufficient Dynamics 365 Sales Enterprise licenses for production but may need to review other licenses for compatibility.
    6. Backup and Recovery:
      • Managed environments often come with extended backup options, which can be a significant advantage for production.
    Negatives of Managed Environments
    • Reduced Flexibility: Managed environments are less adaptable for quick changes or experimentation.
    • Dependency Management: Removing or updating managed solutions can be complex if dependencies exist.
    • Learning Curve: Teams accustomed to unmanaged environments may need time to adapt to the restrictions and processes of Managed Environments.
    Recommendations
    • Test Environment: Consider keeping the test environment unmanaged for flexibility during development and testing.
    • Production Environment: Converting to Managed is advisable for better governance, security, and stability.
    Hope this helps! 
  • Verified answer
    AS-24052230-0 Profile Picture
    AS-24052230-0 14 on at
    I am a big fan of Managed Solutions and Managed environments; however, when there is an issue with either, then you might be on the phone with Microsoft support for a fair amount of time.
     
    Key areas that cause issues
    1) Creating a field in "DEV" , Deploying it to the downstream environments as MANAGED and then 
    DELETING the field in DEV and creating a new field with the same schema name. To mitigate this risk ALWAYS rename fields to Ztobedeleted - [field name] and then use upgrade and other best practices for removing the set of Ztobedeleted fields in downstream environments.
     
    2) Alternate Keys and Keys: If you use alternate keys, they have some "Delete" limitations so be careful with keys.
  • Suggested answer
    Satyam Prakash Profile Picture
    Satyam Prakash 1,089 on at

    Hi,

    Converting your Test and Prod environments to Managed from Unmanaged involves a few considerations:

     

    • Licensing Impact: Managed environments may require premium licenses for all users, potentially increasing costs if you have non-premium users accessing them.

    • Change Control: Once managed, you can’t edit components directly in Test/Prod; changes must flow from Dev (unmanaged) as managed solutions, enforcing stricter ALM but limiting flexibility.

    • Conversion Effort: You’ll need to export unmanaged solutions from Dev as managed, test thoroughly, and ensure all customizations are captured—missed components could cause issues.

    • Negatives vs. Unmanaged: There is less direct control in Managed environments, and dependency on Dev for updates can slow urgent fixes.

       

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
ManoVerse Profile Picture

ManoVerse 192 Super User 2026 Season 1

#2
11manish Profile Picture

11manish 129

#3
CU11031447-0 Profile Picture

CU11031447-0 100

Last 30 days Overall leaderboard

Featured topics

Hide selecting Contact for potential customer when creating quote

Product updates

Dynamics 365 release plans