Skip to content

Commit 80f902a

Browse files
Merge pull request #226199 from csmulligan/csmulligan-b2b-mfa-tutorial
[B2B] Freshness update for b2b-tutorial-require-mfa (ADO-63711)
2 parents accfa65 + 2508e61 commit 80f902a

File tree

2 files changed

+7
-5
lines changed

2 files changed

+7
-5
lines changed

articles/active-directory/external-identities/b2b-tutorial-require-mfa.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ services: active-directory
66
ms.service: active-directory
77
ms.subservice: B2B
88
ms.topic: tutorial
9-
ms.date: 01/07/2022
9+
ms.date: 02/03/2023
1010

1111
ms.author: cmulligan
1212
author: csmulligan
@@ -50,7 +50,7 @@ If you don’t have an Azure subscription, create a [free account](https://azure
5050

5151
To complete the scenario in this tutorial, you need:
5252

53-
- **Access to Azure AD Premium edition**, which includes Conditional Access policy capabilities. To enforce MFA, you need to create an Azure AD Conditional Access policy. MFA policies are always enforced at your organization, regardless of whether the partner has MFA capabilities.
53+
- **Access to [Azure AD Premium edition](/security/business/identity-access/azure-active-directory-pricing)**, which includes Conditional Access policy capabilities. To enforce MFA, you need to create an Azure AD Conditional Access policy. MFA policies are always enforced at your organization, regardless of whether the partner has MFA capabilities.
5454
- **A valid external email account** that you can add to your tenant directory as a guest user and use to sign in. If you don't know how to create a guest account, see [Add a B2B guest user in the Azure portal](add-users-administrator.md).
5555

5656
## Create a test guest user in Azure AD

articles/active-directory/external-identities/current-limitations.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,14 +6,16 @@ services: active-directory
66
ms.service: active-directory
77
ms.subservice: B2B
88
ms.topic: conceptual
9-
ms.date: 01/31/2022
9+
ms.date: 02/13/2023
1010

1111
ms.author: mimart
1212
author: msmimart
1313
manager: celestedg
1414
ms.reviewer: elisolMS
1515

16-
ms.collection: M365-identity-device-management
16+
ms.collection: content-health, M365-identity-device-management
17+
18+
# Customer intent: As a tenant administrator, I want to know about the current limitations for Azure AD B2B collaboration.
1719
---
1820

1921
# Limitations of Azure AD B2B collaboration
@@ -23,7 +25,7 @@ Azure Active Directory (Azure AD) B2B collaboration is currently subject to the
2325
With Azure AD B2B, you can enforce multi-factor authentication at the resource organization (the inviting organization). The reasons for this approach are detailed in [Conditional Access for B2B collaboration users](authentication-conditional-access.md). If a partner already has multi-factor authentication set up and enforced, their users might have to perform the authentication once in their home organization and then again in yours.
2426

2527
## Instant-on
26-
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.
28+
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're writing an app using our API, then retries with some back-off is a good, defensive practice to alleviate this issue.
2729

2830
## Azure AD directories
2931
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](../enterprise-users/directory-service-limits-restrictions.md).

0 commit comments

Comments
 (0)