reviewer edits

Author: msmimart

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

@@ -32,7 +32,7 @@ Azure AD B2B is subject to Azure AD service directory limits. For details about
 [National clouds](https://docs.microsoft.com/azure/active-directory/develop/authentication-national-cloud) are physically isolated instances of Azure. B2B collaboration is not supported across national cloud boundaries. For example, if your Azure tenant is in the public, global cloud, you can't invite a user whose account is in a national cloud. To collaborate with the user, ask them for another email address or create a member user account for them in your directory.
 
 ## Azure US Government clouds
-B2B Collaboration is available only in certain Azure US Government tenants. In supported US Government cloud tenants, only users who are located in other US Government cloud tenants can be invited for B2B collaboration. If an invitee is outside the US Government cloud, the invitation will fail or the user will be unable to redeem the invitation. For details about other limitations, see [Azure Active Directory Premium P1 and P2 Variations](https://docs.microsoft.com/azure/azure-government/documentation-government-services-securityandidentity#azure-active-directory-premium-p1-and-p2).
+Within the Azure US Government cloud, B2B collaboration is currently only supported between tenants that are both within Azure US Government cloud and that both support B2B collaboration. If you invite a user in a tenant that isn't part of the Azure US Government cloud or that doesn't yet support B2B collaboration, the invitation will fail or the user won't be able to redeem the invitation. For details about other limitations, see [Azure Active Directory Premium P1 and P2 Variations](https://docs.microsoft.com/azure/azure-government/documentation-government-services-securityandidentity#azure-active-directory-premium-p1-and-p2).
 
 ### How can I tell if B2B collaboration is available in my Azure US Government tenant?
 To find out if your Azure US Government cloud tenant supports B2B collaboration, do the following:

articles/active-directory/b2b/troubleshoot.md

@@ -96,7 +96,7 @@ As of November 18, 2019, guest users in your directory (defined as user accounts
 
 ## In an Azure US Government tenant, I can't invite a B2B collaboration guest user
 
-B2B collaboration is limited to certain tenants in the Azure US Government cloud. For details and limitations, see [Azure Active Directory Premium P1 and P2 Variations](https://docs.microsoft.com/azure/azure-government/documentation-government-services-securityandidentity#azure-active-directory-premium-p1-and-p2).
+Within the Azure US Government cloud, B2B collaboration is currently only supported between tenants that are both within Azure US Government cloud and that both support B2B collaboration. If you invite a user in a tenant that isn't part of the Azure US Government cloud or that doesn't yet support B2B collaboration, you'll get an error. For details and limitations, see [Azure Active Directory Premium P1 and P2 Variations](https://docs.microsoft.com/azure/azure-government/documentation-government-services-securityandidentity#azure-active-directory-premium-p1-and-p2).
 
 
 ## Next steps

articles/azure-government/documentation-government-services-securityandidentity.md

@@ -145,12 +145,12 @@ The following Azure Active Directory Premium P1 features are currently not avail
 - Group-Based Licensing
 - Azure Active Directory Domain Services
 - Cloud App Security
-- B2B Collaboration is available only in certain Azure US Government tenants. (See [How can I tell if B2B collaboration is available in my tenant?](https://docs.microsoft.com/azure/active-directory/b2b/current-limitations#how-can-I-tell-if-b2b-collaboration-is-available-in-my-tenant)) This feature is not available in other Azure Government tenants ([vote for this feature](https://feedback.azure.com/forums/558487-azure-government/suggestions/20588554-azure-ad-b2b-in-azure-government)).
+- B2B Collaboration is available in Azure US Government tenants created after June, 2019. Over time, more tenants will get access to this functionality. (See [How can I tell if B2B collaboration is available in my tenant?](https://docs.microsoft.com/azure/active-directory/b2b/current-limitations#how-can-I-tell-if-b2b-collaboration-is-available-in-my-tenant)) This feature is not available in other Azure Government tenants ([vote for this feature](https://feedback.azure.com/forums/558487-azure-government/suggestions/20588554-azure-ad-b2b-in-azure-government)).
 
 The following features have known limitations in Azure Government:
 
 - Limitations with B2B Collaboration in supported Azure US Government tenants:
-  - Currently, only users who are located in other US Government cloud tenants can be invited for B2B collaboration. If the invitee is outside the US Government cloud, the invitation will fail or the user will be unable to redeem the invitation.
+  - B2B collaboration is currently only supported between tenants that are both within Azure US Government cloud and that both support B2B collaboration. If you invite a user in a tenant that isn't part of the Azure US Government cloud or that doesn't yet support B2B collaboration, the invitation will fail or the user will be unable to redeem the invitation.
   - B2B collaboration via Power BI is not supported. When you invite a guest user from within Power BI, the B2B flow is not used and the guest user won't appear in the tenant's user list. If a guest user is invited through other means, they'll appear in the Power BI user list, but any sharing request to the user will fail and display a 403 Forbidden error. 
   - Office 365 Groups are not supported for B2B users and can't be enabled.
   - Some SQL tools such as SSMS require you to set the appropriate cloud parameter. In the tool's Azure Service setup options, set the cloud parameter to Azure US Government.