Merge pull request #47889 from msmimart/mm-directory-limits

added link to the Azure AD service limits article

Author: PRMerger7

articles/active-directory/b2b/current-limitations.md

@@ -24,10 +24,13 @@ With Azure AD B2B, you can enforce multi-factor authentication at the resource o
 ## Instant-on
 In the B2B collaboration flows, we add users to the directory and dynamically update them during invitation redemption, app assignment, and so on. The updates and writes ordinarily happen in one directory instance and must be replicated across all instances. Replication is completed once all instances are updated. Sometimes when the object is written or updated in one instance and the call to retrieve this object is to another instance, replication latencies can occur. If that happens, refresh or retry to help. If you are writing an app using our API, then retries with some back-off is a good, defensive practice to alleviate this issue.
 
+## Azure AD directories
+Azure AD B2B is subject to Azure AD service directory limits. For details about the number of directories a user can create and the number of directories to which a user or guest user can belong, see [Azure AD service limits and restrictions](https://docs.microsoft.com/azure/active-directory/users-groups-roles/directory-service-limits-restrictions).
+
 ## Next steps
 
 See the following articles on Azure AD B2B collaboration:
 
 - [What is Azure AD B2B collaboration?](what-is-b2b.md)
-- [Delegate B2bB collaboration invitations](delegate-invitations.md)
+- [Delegate B2B collaboration invitations](delegate-invitations.md)