Add warning about changing IdPs or tenants (#37946)

Co-authored-by: Greg Padak <gpadak@github.com>
coolaj86 · Jun 28, 2023 · b3d9dd5 · b3d9dd5
1 parent 29484cf
commit b3d9dd5
Showing 1 changed file with 6 additions and 0 deletions.
diff --git a/...users-for-iam/migrating-your-enterprise-to-a-new-identity-provider-or-tenant.md b/...users-for-iam/migrating-your-enterprise-to-a-new-identity-provider-or-tenant.md
@@ -18,6 +18,12 @@ topics:
 
 While using {% data variables.product.prodname_emus %}, you may need to migrate your enterprise to a new IdP or Azure AD tenant. For example, you might be ready to migrate from a test environment to your production environment.
 
+{% warning %}
+
+**Warning**: Migrating to a new identity provider or tenant can cause disruption to integrations and automated flows in your enterprise. When your current SAML identity provider is disabled, {% data variables.product.pat_generic_plural %} and SSH keys associated with {% data variables.enterprise.prodname_managed_users %} will be deleted. You should plan for a migration window after configuring your new identity provider, during which you can create and deploy new keys to your integrations where necessary.
+
+{% endwarning %}
+
 Before you migrate your {% data variables.enterprise.prodname_emu_enterprise %} to a new IdP or tenant, determine whether the values of the normalized SCIM `userName` attribute will remain the same for your {% data variables.enterprise.prodname_managed_users %} in the new environment. For more information about username normalization, see "[AUTOTITLE](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)."
 
 If the normalized SCIM `userName` values will remain the same after the migration, you can complete the migration by yourself. For instructions, see "[Migrating when the normalized SCIM `userName` values will remain the same](#migrating-when-the-normalized-scim-username-values-will-remain-the-same)."