Skip to content

Commit 3cf77fd

Browse files
committed
edits
1 parent c270393 commit 3cf77fd

File tree

3 files changed

+7
-7
lines changed

3 files changed

+7
-7
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ Azure AD B2B is subject to Azure AD service directory limits. For details about
3232
[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.
3333

3434
## Azure US Government clouds
35-
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/active-directory/develop/authentication-national-cloud#azure-active-directory-premium-p1-and-p2) in the Azure Government Security + Identity article.
35+
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).
3636

3737
### How can I tell if B2B collaboration is available in my Azure US Government tenant?
3838
To find out if your Azure US Government cloud tenant supports B2B collaboration, do the following:
@@ -43,8 +43,8 @@ To find out if your Azure US Government cloud tenant supports B2B collaboration,
4343

4444
2. Find `"tenant_region_scope"` in the JSON response:
4545

46-
- If `"tenant_region_scope":"USGOV”` appears, B2B is supported.
47-
- If `"tenant_region_scope":"USG"` appears, B2B is not supported.
46+
- If `"tenant_region_scope":"USGOV”` appears, B2B is supported.
47+
- If `"tenant_region_scope":"USG"` appears, B2B is not supported.
4848

4949

5050
## Next steps

articles/active-directory/b2b/troubleshoot.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -96,7 +96,7 @@ As of November 18, 2019, guest users in your directory (defined as user accounts
9696

9797
## In an Azure US Government tenant, I can't invite a B2B collaboration guest user
9898

99-
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/active-directory/develop/authentication-national-cloud#azure-active-directory-premium-p1-and-p2) in the Azure Government Security + Identity article.
99+
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).
100100

101101

102102
## Next steps

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -145,14 +145,14 @@ The following Azure Active Directory Premium P1 features are currently not avail
145145
- Group-Based Licensing
146146
- Azure Active Directory Domain Services
147147
- Cloud App Security
148-
- B2B Collaboration is available only in certain Azure US Government tenants ([find out how to tell if B2B collaboration is available in your 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)).
148+
- 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)).
149149

150150
The following features have known limitations in Azure Government:
151151

152152
- Limitations with B2B Collaboration in supported Azure US Government tenants:
153153
- 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.
154-
- 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 (with a 403 forbidden error).
155-
- Office 365 Groups aren't supported for B2B users and can't be enabled.
154+
- 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.
155+
- Office 365 Groups are not supported for B2B users and can't be enabled.
156156
- 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.
157157

158158
- Limitations with the Azure Active Directory App Gallery:

0 commit comments

Comments
 (0)