Updating geo-to-geo migration doc according to latest guidelines #2668
Conversation
|
Learn Build status updates of commit a9db19b:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| power-platform/admin/geo-to-geo-migrations.md | Details |
power-platform/admin/geo-to-geo-migrations.md
- Line 54, Column 3: [Warning: file-not-found - See documentation]
Invalid file link: 'admin/managed-environment-overview.md'. - Line 99, Column 5: [Warning: file-not-found - See documentation]
Invalid file link: './admin/wp-onpremises-gateway.md'. - Line 139, Column 25: [Warning: file-not-found - See documentation]
Invalid file link: 'developer/cli/introduction.md'.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
|
|
||
| #### For Power Apps portals (must be done for each portal in the environments): |
There was a problem hiding this comment.
Are these steps anywhere in the updated doc? Can't seem to find them
There was a problem hiding this comment.
Power Apps portals was renamed to Power Pages. I've covered Power Pages steps in the "For components that are in solutions" section above.
The "Reset" action called out here is the same as deleting website host. And the "Provision" action is the same as reactivating the site. I also moved both of these steps to post-migration/after migration since I found that these steps can both be done after migration rather than Reset before migration and Provision after migration. I just think it's a bit easier for customers to follow if all the steps are done together.
| @@ -28,131 +29,146 @@ The Geo Migration feature allows customers to move their environments in a singl | |||
| > - After making a request, expect at least 10 days for the migration to be completed. | |||
| > - Geo migrations are not supported into or out of US GCC, US GCC High, or China. | |||
| > - Geo migrations are restricted into or out of OCE or IND. | |||
| > - The Dynamics 365 Marketing app does not support geo migration, due to component dependencies. For more information, see [Manage your Dynamics 365 Marketing instances](/dynamics365/marketing/manage-marketing-instances). If installed, the Dynamics 365 Marketing app must be uninstalled prior to the migration. | |||
| > - Geo migration is not supported for Microsoft Dataverse for Teams environments. | |||
| > - Dataverse organization linked to a finance and operations organization is not supported. | |||
There was a problem hiding this comment.
Should we document that FnO is supported as long as both are moved? And it requires unlinking?
There was a problem hiding this comment.
I think we can leave out internal details such as moving FnO and unlinking as long as there's no further impact to the customer (other than the expected downtime).
No description provided.