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

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / Tenants, Environments,...
Power Apps
Answered

Tenants, Environments, Regions

(2) ShareShare
ReportReport
Posted on by 297
I have a complex problem and many questions.
 
I inherited a Microsoft tenant in the Europe region. 
In the tenant is a sandbox environment and a production environment, also in the Europe region.
On the production environment, is a large amount of data in dataverse, with a model driven app, and several flows. The production environment is unmanaged and so is the solution in which all the data and app sits. 
 
  1. Is there any benefit to moving everything into the South Africa region?
  2. Is it even possible to move a tenant from the Europe region to South Africa region?
  3. What would the process be to change the Production environment from unmanaged to managed?
  4. What would the process be to change the solution from unmanaged to managed?
I feel a bit lost here.
I have the same question (0)
  • Suggested answer
    wolenberg_ Profile Picture
    1,476 Super User 2026 Season 1 on at
    Hi @Hilda Steyn , 

    You cannot move an entire Microsoft tenant from Europe to South Africa directly; geo‑to‑geo migrations are limited, require Microsoft approval, and are usually only available for specific scenarios. The better path is to create a new environment in South Africa if you need local data residency. As for managed vs. unmanaged solutions, you don’t “convert” them you export your unmanaged solution as managed and then import it into the target environment. 

    So answering your questions:

    1. You can’t move the tenant itself; only environments can sometimes be migrated with Microsoft’s help.
    2.  The practical option is to create a new environment in South Africa if needed.
    3.  To switch from unmanaged to managed solutions, export as managed from dev and import into production.
    You can see more references bellow:
     

    ✨ If my response helped resolve your issue, please mark it as ✅ Accepted Answer and give it a ❤️ like — it helps others in the community find solutions faster. Thank you!



     
     
  • Verified answer
    11manish Profile Picture
    2,207 on at
    You’re dealing with several platform-level architecture topics in the Microsoft Power Platform, especially around environment geography, solution lifecycle management, and managed vs unmanaged solutions in Microsoft Dataverse.
     
    I’ll break down each of your questions with practical guidance.
    Is there any benefit to moving from Europe to South Africa?
    Usually no, unless your users and data residency requirements are primarily in South Africa.
     
    Potential benefits
    • Lower latency for users located in South Africa
    • Data residency compliance if regulations require local storage
    • Possibly simpler integration with other systems hosted in South Africa
    Potential downsides
    • South Africa regions generally have fewer Azure / Power Platform services available
    • Microsoft sometimes rolls out new features later in smaller regions
    • Migration effort is significant
    If most users are in Europe, staying in the Europe region is typically better.
     
    Can you move a tenant from Europe to South Africa?
     
    No.
    A Microsoft tenant region cannot be moved once created.
    However, you can move environments or recreate them.
    Possible approaches
     
    Option A — Environment Copy (same region only)
    Sandbox → Production copy works only within the same geography.
     
    So this cannot move to South Africa.
    Option B — Recreate environment in new region
    Steps:
    • Create a new environment in South Africa
    • Export solutions
    • Import them
    • Migrate data
    This is effectively a migration project, not a simple move.
     
    Tools typically used:
    • Configuration Migration Tool
    • Power Platform Dataflows
    • Azure Data Factory
    • Dataverse API / ETL tools
    Changing Production Environment from Unmanaged to Managed
    Important point:
    • You cannot convert an environment itself from unmanaged to managed.
    • The environment simply hosts solutions.
    • What matters is solution management model.
    Your current situation:
    Production
     └ Unmanaged solution
    Best practice architecture:
    DEV (unmanaged)
     → TEST
     → PROD (managed)
     
    So you should create a proper ALM pipeline.
    Converting an Unmanaged Solution to Managed
     
    You cannot directly convert an existing unmanaged solution in Production into managed.
     
    Instead, the process is:
     
    Step 1 — Create a Development Environment
    Create a new Dev environment in Power Platform Admin Center.
     
    Step 2 — Move your solution to Dev
    Export from Production:
    Export Solution
    (unmanaged)
    Import into Dev.
     
    Now Dev becomes the source of truth.
    Step 3 — Clean up and organize
    In Dev:
    • separate components into proper solutions
    • remove environment-specific customizations
    • fix dependencies
    Step 4 — Export as Managed
    From Dev:
    • Export Solution → Managed
    Step 5 — Import Managed Solution to Production
     
    Production will now contain:
    • Managed solution
     
    instead of unmanaged components.
  • Hilda Steyn Profile Picture
    297 on at
    @11manish Thank you for that. 
     
    I understand that I have to export the unmanaged solution from prod and import to dev and I have done that. 
    I understand that I have to export a managed solution from dev and import into prod, however, I cannot import the managed environment into prod as long as the unmanaged one is there. And I am so scared of losing data. What are the steps here to ensure no data loss?
     
  • Suggested answer
    pavanmanideep Profile Picture
    574 Power Up Champ - 2025 on at
    @Hilda Steyn You can't uninstall the unmanaged solution in Production, but that doesn't stop you from importing an managed solution to Production from Dev.
     
    You can go ahead and you wouldn't have any data loss as old unmanaged solutions stays there as is and practically there is no way to remove the unmanaged solutions from Production. Going further you may make changes to the unmanaged solution and deploy to Production. I saw many organizations initially started deploying Unmanaged Solutions but later when project matures, they wanted to align as per best practice deploying managed solutions to Production.
     
    Hope this helps...
     
    If any more information is needed, please don't hesitate to let me know.
     
    Cheers,
    PMDY
    Microsoft MVP(Power Apps)
     
  • 11manish Profile Picture
    2,207 on at
     
    Your concern is valid. Moving from an unmanaged solution in Production to a managed ALM model in Microsoft Power Platform / Microsoft Dataverse must be done carefully to avoid deleting components or affecting data. The good news is: solution imports normally do NOT delete business data (records), but there is a correct migration approach.
     
    * before touching anything, take full environment backup
     

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 Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Congratulations to the April Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Apps

#1
Vish WR Profile Picture

Vish WR 1,009

#2
11manish Profile Picture

11manish 672

#3
Valantis Profile Picture

Valantis 628

Last 30 days Overall leaderboard