Microsoft 365 – Power Platform – Empowering your Learning Journey: A Comprehensive Guide to Power Platform for Beginners – Unleashing the Power of Managed Environments in Power Platform: A Superhero Toolkit for Admins – Part 10

“The beginning is the most important part of the work.”

Hey there, Power Platform explorers!

In the dynamic realm of Power Platform, where innovation meets functionality, administrators hold the key to steering the course of efficient management. One such tool that has emerged as a superhero in our toolkit is Managed Environments. In this article, we’ll explore the superpowers bestowed upon us through Managed Environments and how we can wield these capabilities to enhance control, insights, and security within the Power Platform.

Empower your learning journey with Power Apps!

• Foundations: Master Power Apps and the Power Platform dynamics. Read Part 1.
• Exploration: Navigate Power Apps’ enchanting features. Explore Part 2.
• No Code Magic: Unleash creativity with Canvas Apps. Discover Part 3.
• Business Decisions: SPFx vs Power Apps insights. Decide with Part 4.
• Hands-On Creation: Team-guided Canvas App creation. Create with Part 5.
• App Mobility: Learn Power Apps basics – Moving Your Apps Around. Explore Part 6.
• Navigating Environments: A Beginner’s Guide. Dive into Part 7.
• Creating and Managing Environments: Part 8 – A Comprehensive Guide for Beginners. Read Part 8 Here
• Let’s Explore Power Platform Admin Center: A Beginner’s Adventure – Part 9. For the detailed guide, Read Part 9 Here.

Key Takeaways from this article

In this article:

• Introduction to Managed Environments:
  • Learn about the role of Managed Environments in Power Platform management.
  • Understand the benefits for administrators in terms of control, insights, and security.
• Enabling and Disabling Managed Environments:
  • Explore the process of enabling and disabling Managed Environments.
  • Understand PowerShell commands for efficient management.
• Additional Admin Steps:
  • Steps for enabling Managed Environments in the Power Platform admin center.
  • Configuration details, including Solution Checker Enforcement and Managed Environment Insights.
• Enhancing Control: Disabling with PowerShell:
  • A concise guide on using PowerShell to disable Managed Environments.
  • Verification steps and important considerations.
• Wisdom in Wielding Superpowers:
  • Cautionary notes before disabling Managed Environments.

Managed Environment

• Managed Environments in the Power Platform are like a set of tools that help us, the people in charge (admins), control and keep an eye on what’s happening in the Power Platform.
• These tools make things easier for administrators, reducing our workload and giving us better information.
• Now, to use these Managed Environments, we need to be an admin with specific roles. Once we have the right permissions, we can enable Managed Environments in the Power Platform admin center.

Enabling and Disabling Managed Environments: A Toggle for Efficiency:

• Enabling Managed Environments is akin to giving us a set of superpowers that streamline control and management.
• Admins with specific roles can effortlessly activate Managed Environments within the Power Platform admin center, marking their territory with the proud badge of “Managed.”
• However, caution is advised when considering the option to disable.
• We can utilize PowerShell commands, ensuring we have the Environment ID handy. Once disabled, the environment reverts to being “Not Managed.”
• A crucial note: thorough evaluation is necessary to ensure no vital features depend on Managed Environments before making the switch.

Additional Steps for Admins: Enabling Managed Environments:

In the journey of harnessing the superpowers of Managed Environments, we need a clear roadmap for activation. Here are the steps to enable Managed Environments seamlessly:

Navigate to the Power Platform Admin Center:

• Begin the journey by entering the Power Platform admin center, the central hub for platform administration.

Select Environments:

• Within the admin center, locate and click on the “Environments” option. This is the starting point for initiating changes to environment configurations.

Enable Managed Environments:

• In the context menu of the chosen environment, find and select “Enable Managed Environments.” Alternatively, we can use the command bar and choose “Enable Managed Environments.”

Configuration Process:

• A new window or interface will appear, allowing admins to configure specific settings associated with Managed Environments.
• Solution Checker Enforcement: A Guardian for Customizations:

• Enter Solution Checker, the vigilant guardian for customizations.
  • Admins gain unprecedented control with the ability to block or warn about critical issues during solution imports.
  • To sweeten the deal, admins receive email summaries that keep them informed about solution quality and import status, providing a comprehensive view of their platform’s health.
• Managed Environment Insights: The Backstage Pass to Analytics:

• Managed Environment Insights provides admins a backstage pass to analytics, delivering a comprehensive view of platform usage.
  • The Weekly Digest serves as a VIP newsletter, delivering insights on top apps, makers, and even inactive resources.
  • It’s the key to understanding and optimizing the Power Platform’s performance.
• Sharing Controls: Rein in the Power of Sharing:

• Admins are granted the power to control the sharing of canvas apps within Managed Environments.
  • By setting rules and exclusions, admins ensure that sharing aligns with organizational objectives.
  • These controls act as guardians, ensuring that the sharing of apps adheres to established guidelines.
• Data Policies: Security Detail for Your Data:

• Managed Environments bring forth a security detail for data through enforced Data Loss Prevention (DLP) policies.
  • Admins can navigate and identify applied data policies effortlessly, fostering a secure and standardized approach to data management within the organization.
• License Considerations: Power with Flexibility:
  • With great power comes great responsibility, and Managed Environments come with their own licensing considerations.
  • During the public preview, the strict enforcement of premium license requirements is relaxed, offering admins a taste of premium features without the immediate commitment.

Save or Enable:

• After configuring the settings according to organizational needs, we can proceed to either “Save” or “Enable,” depending on the system’s prompts.

Observing the Change:

• Once the process is complete, observe the changes in the environment. Specifically, check the ‘Managed’ property of the environment, which should now be set to ‘Yes.’

By following these steps, we can seamlessly enable Managed Environments, unlocking a suite of tools designed to streamline control, enhance insights, and fortify security within the Power Platform. This additional guidance ensures that we have a straightforward path to activating these powerful features and optimizing our Power Platform management experience.

Enhancing Control: Disabling Managed Environments with PowerShell:

As we delve deeper into the nuances of managing Power Platform environments, it’s crucial to understand the steps involved in disabling Managed Environments when needed. Here’s a concise guide for admins looking to harness the power of PowerShell in this process:

Steps to Disable Managed Environments:

• Open the PowerShell Console:
  • Launch the PowerShell console, our command hub for performing administrative tasks.
• Connect to Power Apps Account:

• Utilize the Add-PowerAppsAccount command to establish a connection to the Power Apps account. This step ensures that the subsequent commands are executed within the appropriate context.
• Retrieve Environment ID:

• To initiate the disable command, the unique ‘Environment ID’ of the managed environment is required. Copy this crucial identifier from the Power Platform admin center.
• Execute PowerShell Command:
  • Execute the following PowerShell command, replacing the placeholder ‘Environment ID’ with the actual identifier:

Powershell

$UpdatedGovernanceConfiguration = [pscustomobject]@{

    protectionLevel = "Basic"

}

Set-AdminPowerAppEnvironmentGovernanceConfiguration -EnvironmentName <Environment ID> -UpdatedGovernanceConfiguration $UpdatedGovernanceConfiguration

Upon successful execution, we should receive a 202 code.

Powering Up Environments: A Recipe for Configuration with PowerShell

• Create a Configuration:
  • We’re creating a set of instructions (a configuration) using PowerShell. We’re calling it $UpdatedGovernanceConfiguration.
  • This set of instructions says, “Let’s set the protection level to ‘Basic.'”
• Apply Configuration to an Environment:
  • Now, we want to use these instructions for a specific place in the Power Platform, like a playground or work area. This place is called an “environment.”
  • <Environment ID> is like the address of that environment. We need to replace <Environment ID> with the actual address.
  • We’re telling PowerShell to apply our set of instructions to that environment.
• In Simpler Terms:
  • Think of the configuration as a recipe. We’re saying, “Make it Basic.”
  • The environment is like the kitchen where we want to use this recipe.
  • We’re using PowerShell to tell the kitchen (Power Platform) to follow our recipe and make things Basic in that specific place.
• Important Reminder:
  • Before doing this, make sure you have the right permissions and access, like being a kitchen manager (administrator) who can decide how things work in that kitchen (Power Platform).
  • These commands are like notes for the kitchen staff (PowerShell) to follow, so they should be used by someone who understands how the kitchen (Power Platform) operates.

Verify Changes:

• Return to the Power Platform admin center to observe the changes. Specifically, check the ‘Managed’ property, which should now be set to ‘No.’

Important Notes:

• Precaution Before Disabling:
  • Before initiating the disable process, administrators must ensure that none of the Managed Environments capabilities are actively in use. This prevents any disruptions to ongoing operations.
• License Considerations:
  • Managed Environments are included as an entitlement with standalone licenses such as Power Apps, Power Automate, Power Virtual Agents, Power Pages, and Dynamics 365. Trial licenses can be leveraged for users in Managed Environments, subject to specific restrictions.
• Developer Plan Exclusion:
  • Notably, Managed Environments aren’t included as an entitlement in the Developer Plan when users run their assets. Admins should consider this distinction when managing different user plans.

In mastering the art of managing Power Platform environments, admins equipped with PowerShell commands can seamlessly disable Managed Environments, ensuring a strategic and controlled approach to platform governance.

Important Notes: Wisdom in Wielding Superpowers:

To sum it up, this article is all about Managed Environments in the Power Platform. It’s like a superhero tool for administrators, giving them control and insights. The article explains how to enable and disable Managed Environments, use PowerShell commands, and take additional steps for effective management. It’s a guide for admins to use these superpowers wisely, with a reminder to be cautious and understand how Managed Environments fit alongside other tools like the Center of Excellence (CoE) Kit. Ultimately, it helps admins navigate and manage their Power Platform efficiently.

Also get my article updates on my social media handles.

Twitter – https://twitter.com/PrajyotYawalkar?t=oovP0r9FnDtz5nNSJGKO0Q&s=09

LinkedIn – https://www.linkedin.com/in/prajyot-yawalkar-093716224/

Have a wonderful day.

Thanks for reading.