Cross-tenant access settings
Microsoft's edit ·
Microsoft's commit message in MicrosoftDocs/entra-docs · commit 44d3b54 · +1 −2 lines · also on GitHub
⋯ 22 unchanged lines
2323
2424
This article covers cross-tenant access settings for managing B2B collaboration and B2B direct connect with external Entra organizations, including across Microsoft clouds. Other settings are available for B2B collaboration with non-Microsoft Entra identities (for example, social identities or non-IT managed external accounts). These [external collaboration settings](external-collaboration-settings-configure.md) include options for restricting guest user access, specifying who can invite guests, and allowing or blocking domains.
2525
26
−> [!IMPORTANT]
27
−> Microsoft started to move customers using cross-tenant access settings to a new storage model on August 30, 2023. You may notice an entry in your audit logs informing you that your cross-tenant access settings were updated as our automated task migrates your settings. For a brief window while the migration processes, you'll be unable to make changes to your settings. If you're unable to make a change, wait a few moments and try the change again. Once the migration completes, [you'll no longer be capped with 25kb of storage space](./faq.yml#how-many-organizations-can-i-add-in-cross-tenant-access-settings-) and there will be no more limits on the number of partners you can add.
26
+There are no limits to the number of organizations you can add in cross-tenant access settings.
2827
2928
## Manage external access with inbound and outbound settings
3029
⋯ 181 unchanged lines
Microsoft's Markdown source from MicrosoftDocs/entra-docs, © Microsoft Corporation, under MIT. Changed lines with up to 3 unchanged lines around each; ChangeIntel kept this copy 10 Oct 07:21 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.