Skip to content

Commit acccf77

Browse files
Merge pull request #227956 from csmulligan/csmulligan-b2b-freshness-updates
[B2B] Content freshness and SEO updates (ADO-65030)
2 parents 7ef0eff + 7735fdd commit acccf77

File tree

4 files changed

+25
-23
lines changed

4 files changed

+25
-23
lines changed

articles/active-directory/external-identities/b2b-direct-connect-overview.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,17 @@
11
---
2-
title: B2B direct connect overview - Azure AD
2+
title: B2B direct connect Azure AD overview
33
description: Azure Active Directory B2B direct connect lets users from other Azure AD tenants seamlessly sign in to your shared resources via Teams shared channels. There's no need for a guest user object in your Azure AD directory.
44

55
services: active-directory
66
ms.service: active-directory
77
ms.subservice: B2B
88
ms.topic: conceptual
9-
ms.date: 10/12/2022
9+
ms.date: 02/20/2023
1010

1111
ms.author: cmulligan
1212
author: csmulligan
1313
manager: celestedg
14-
ms.collection: M365-identity-device-management
14+
ms.collection: engagement-fy23, M365-identity-device-management
1515
---
1616

1717
# B2B direct connect overview
@@ -42,11 +42,11 @@ Azure AD organizations can manage their trust relationships with other Azure AD
4242
> B2B direct connect is possible only when both organizations allow access to and from the other organization. For example, Contoso can allow inbound B2B direct connect from Fabrikam, but sharing isn't possible until Fabrikam also enables outbound B2B direct connect with Contoso. Therefore, you’ll need to coordinate with the external organization’s admin to make sure their cross-tenant access settings allow sharing with you. This mutual agreement is important because B2B direct connect enables limited sharing of data for the users you enable for B2B direct connect.
4343
### Default settings
4444

45-
The default cross-tenant access settings apply to all external Azure AD organizations, except organizations for which you've configured individual settings. Initially, Azure AD blocks all inbound and outbound B2B direct connect capabilities by default for all external Azure AD tenants. You can change these default settings, but typically you'll leave them as-is and enable B2B direct connect access with individual organizations.
45+
The default cross-tenant access settings apply to all external Azure AD organizations, except organizations for which you've configured individual settings. Initially, Azure AD blocks all inbound and outbound B2B direct connect capabilities by default for all external Azure AD tenants. You can change these default settings, but typically you can leave them as-is and enable B2B direct connect access with individual organizations.
4646

4747
### Organization-specific settings
4848

49-
You can configure organization-specific settings by adding the organization and modifying the cross-tenant access settings. These settings will then take precedence over the default settings for this organization.
49+
You can configure organization-specific settings by adding the organization and modifying the cross-tenant access settings. These settings then take precedence over the default settings for this organization.
5050

5151
### Example 1: Allow B2B direct connect with Fabrikam and block all others
5252

@@ -70,7 +70,7 @@ For this scenario to work, Fabrikam also needs to allow B2B direct connect with
7070

7171
### Example 2: Enable B2B direct connect with Fabrikam's Marketing group only
7272

73-
Starting from the example above, Contoso could also choose to allow only the Fabrikam Marketing group to collaborate with Contoso's users through B2B direct connect. In this case, Contoso will need to obtain the Marketing group's object ID from Fabrikam. Then, instead of allowing inbound access to all Fabrikam's users, they'll configure their Fabrikam-specific access settings as follows:
73+
Starting from the example above, Contoso could also choose to allow only the Fabrikam Marketing group to collaborate with Contoso's users through B2B direct connect. In this case, Contoso needs to obtain the Marketing group's object ID from Fabrikam. Then, instead of allowing inbound access to all Fabrikam's users, they'll configure their Fabrikam-specific access settings as follows:
7474

7575
- Allow inbound access to B2B direct connect for Fabrikam's Marketing group only. Contoso specifies Fabrikam's Marketing group object ID in the allowed users and groups list.
7676
- Allow inbound access to all internal Contoso applications by Fabrikam B2B direct connect users.
@@ -105,11 +105,11 @@ In your cross-tenant access settings, you can use **Trust settings** to trust cl
105105

106106
Currently, B2B direct connect enables the Teams Connect shared channels feature. B2B direct connect users can access an external organization's Teams shared channel without having to switch tenants or sign in with a different account. The B2B direct connect user’s access is determined by the shared channel’s policies.
107107

108-
In the resource organization, the Teams shared channel owner can search within Teams for users from an external organization and add them to the shared channel. After they're added, the B2B direct connect users can access the shared channel from within their home instance of Teams, where they collaborate using features such as chat, calls, file-sharing, and app-sharing. For details, see [Overview of teams and channels in Microsoft Teams](/microsoftteams/teams-channels-overview). For details about the resources, files, and applications, that are available to the B2B direct connect user via the Teams shared channel, refer to [Chat, teams, channels, & apps in Microsoft Teams](/microsoftteams/deploy-chat-teams-channels-microsoft-teams-landing-page).
108+
In the resource organization, the Teams shared channel owner can search within Teams for users from an external organization and add them to the shared channel. After they're added, the B2B direct connect users can access the shared channel from within their home instance of Teams, where they collaborate using features such as chat, calls, file-sharing, and app-sharing. For details, see [Overview of teams and channels in Microsoft Teams](/microsoftteams/teams-channels-overview). For details about the resources, files, and applications that are available to the B2B direct connect user via the Teams shared channel refer to [Chat, teams, channels, & apps in Microsoft Teams](/microsoftteams/deploy-chat-teams-channels-microsoft-teams-landing-page).
109109

110110
## B2B direct connect vs. B2B collaboration
111111

112-
B2B collaboration and B2B direct connect are two different approaches to sharing with users outside of your organization. You'll find a [feature-to-feature comparison](external-identities-overview.md#comparing-external-identities-feature-sets) in the External Identities overview. Here, we'll discuss some key differences in how users are managed and how they access resources.
112+
B2B collaboration and B2B direct connect are two different approaches to sharing with users outside of your organization. You can find a [feature-to-feature comparison](external-identities-overview.md#comparing-external-identities-feature-sets) in the External Identities overview, where we discuss some key differences in how users are managed, and how they access resources.
113113

114114
### User access and management
115115

-86.3 KB
Loading

articles/active-directory/external-identities/one-time-passcode.md

Lines changed: 10 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -7,19 +7,21 @@ services: active-directory
77
ms.service: active-directory
88
ms.subservice: B2B
99
ms.topic: how-to
10-
ms.date: 09/16/2022
10+
ms.date: 02/21/2023
1111
ms.author: mimart
1212
author: msmimart
1313
manager: CelesteDG
1414
ms.custom: "it-pro, seo-update-azuread-jan, seoapril2019, contperf-fy21q4-portal"
15-
ms.collection: M365-identity-device-management
15+
ms.collection: engagement-fy23, M365-identity-device-management
16+
17+
# Customer intent: As a tenant administrator, I want to make sure that my users can authenticate themselves with one-time passcode.
1618
---
1719

1820
# Email one-time passcode authentication
1921

2022
The email one-time passcode feature is a way to authenticate B2B collaboration users when they can't be authenticated through other means, such as Azure AD, Microsoft account (MSA), or social identity providers. When a B2B guest user tries to redeem your invitation or sign in to your shared resources, they can request a temporary passcode, which is sent to their email address. Then they enter this passcode to continue signing in.
2123

22-
![Diagram showing an overview of Email one-time passcode.](media/one-time-passcode/email-otp.png)
24+
:::image type="content" source="media/one-time-passcode/email-otp.png" alt-text="Diagram showing an overview of Email one-time passcode.":::
2325

2426
> [!IMPORTANT]
2527
>
@@ -72,7 +74,7 @@ At the time of invitation, there's no indication that the user you're inviting w
7274
7375
### Example
7476

75-
Guest user teri@gmail.com is invited to Fabrikam, which doesn't have Google federation set up. Teri doesn't have a Microsoft account. They'll receive a one-time passcode for authentication.
77+
Guest user nicole@firstupconsultants.com is invited to Fabrikam, which doesn't have Google federation set up. Nicole doesn't have a Microsoft account. They'll receive a one-time passcode for authentication.
7678

7779
## Enable or disable email one-time passcodes
7880

@@ -97,9 +99,9 @@ The email one-time passcode feature is now turned on by default for all new tena
9799
- **Yes**: The toggle is set to **Yes** by default unless the feature has been explicitly turned it off. To enable the feature, make sure **Yes** is selected.
98100
- **No**: If you want to disable the email one-time passcode feature, select **No**.
99101

100-
![Screenshots showing the Email one-time passcode toggle.](media/one-time-passcode/email-one-time-passcode-toggle.png)
102+
:::image type="content" source="media/one-time-passcode/email-one-time-passcode-toggle.png" alt-text="Screenshots showing the Email one-time passcode toggle.":::
101103

102-
1. Select **Save**.
104+
6. Select **Save**.
103105

104106
## Frequently asked questions
105107

@@ -125,8 +127,8 @@ When we support the ability to disable Microsoft Account in the Identity provide
125127

126128
**Regarding the change to enable email one-time-passcode by default, does this include SharePoint and OneDrive integration with Azure AD B2B?**
127129

128-
No, the global rollout of the change to enable email one-time passcode by default doesn't include enabling SharePoint and OneDrive integration with Azure AD B2B by default. To learn how to enable integration so that collaboration on SharePoint and OneDrive uses B2B capabilities, or how to disable this integration, see [SharePoint and OneDrive Integration with Azure AD B2B](/sharepoint/sharepoint-azureb2b-integration).
130+
No, the global rollout of the change to enable email one-time passcode by default doesn't include enabling SharePoint and OneDrive integration with Azure AD B2B by default.To learn how to enable or disable the integration of SharePoint and OneDrive with Azure AD B2B for secure collaboration, see [SharePoint and OneDrive Integration with Azure AD B2B](/sharepoint/sharepoint-azureb2b-integration).
129131

130132
## Next steps
131133

132-
Learn about [Identity Providers for External Identities](identity-providers.md).
134+
Learn about [Identity Providers for External Identities](identity-providers.md), and how to reset [redemption status for a guest user](reset-redemption-status.md).

articles/active-directory/external-identities/what-is-b2b.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,17 @@
11
---
2-
title: B2B collaboration overview - Azure AD
2+
title: Azure AD B2B collaboration overview
33
description: Azure Active Directory B2B collaboration supports guest user access so you can securely share resources and collaborate with external partners.
44

55
services: active-directory
66
ms.service: active-directory
77
ms.subservice: B2B
88
ms.topic: overview
9-
ms.date: 02/14/2023
9+
ms.date: 02/20/2023
1010
ms.author: cmulligan
1111
author: csmulligan
1212
manager: celestedg
1313
ms.custom: "engagement-fy23, it-pro, seo-update-azuread-jan"
14-
ms.collection: M365-identity-device-management
14+
ms.collection: engagement-fy23, M365-identity-device-management
1515
---
1616

1717
# B2B collaboration overview
@@ -20,7 +20,7 @@ Azure Active Directory (Azure AD) B2B collaboration is a feature within External
2020

2121
![Diagram illustrating B2B collaboration.](media/what-is-b2b/b2b-collaboration-overview.png)
2222

23-
A simple invitation and redemption process lets partners use their own credentials to access your company's resources. You can also enable self-service sign-up user flows to let external users sign up for apps or resources themselves. Once the external user has redeemed their invitation or completed sign-up, they're represented in your directory as a [user object](user-properties.md). B2B collaboration user objects are typically given a user type of "guest" and can be identified by the #EXT# extension in their user principal name.
23+
A simple invitation and redemption process lets partners use their own credentials to access your company's resources. You can also enable self-service sign-up user flows to let external users sign up for apps or resources themselves. Once the external user has redeemed their invitation or completed sign-up, they're represented in your directory as a [user object](user-properties.md). The user type for these B2B collaboration users is typically set to "guest" and their user principal name contains the #EXT# identifier.
2424

2525
Developers can use Azure AD business-to-business APIs to customize the invitation process or write applications like self-service sign-up portals. For licensing and pricing information related to guest users, refer to [Azure Active Directory External Identities pricing](https://azure.microsoft.com/pricing/details/active-directory/external-identities/).
2626

@@ -101,12 +101,12 @@ Azure AD supports external identity providers like Facebook, Microsoft accounts,
101101

102102
## Integrate with SharePoint and OneDrive
103103

104-
You can [enable integration with SharePoint and OneDrive](/sharepoint/sharepoint-azureb2b-integration) to share files, folders, list items, document libraries, and sites with people outside your organization, while using Azure B2B for authentication and management. The users you share resources with are typically added to your directory as guests, and permissions and groups work the same for these guests as they do for internal users. When enabling integration with SharePoint and OneDrive, you'll also enable the [email one-time passcode](one-time-passcode.md) feature in Azure AD B2B to serve as a fallback authentication method.
104+
You can [enable integration with SharePoint and OneDrive](/sharepoint/sharepoint-azureb2b-integration) to share files, folders, list items, document libraries, and sites with people outside your organization, while using Azure B2B for authentication and management. The users you share resources with are typically guest users in your directory, and permissions and groups work the same for these guests as they do for internal users. When enabling integration with SharePoint and OneDrive, you also enable the [email one-time passcode](one-time-passcode.md) feature in Azure AD B2B to serve as a fallback authentication method.
105105

106106
![Screenshot of the email one-time-passcode setting.](media/what-is-b2b/enable-email-otp-options.png)
107107

108108
## Next steps
109109

110-
- [External Identities pricing](external-identities-pricing.md)
110+
- [Invitation email](invitation-email-elements.md)
111111
- [Add B2B collaboration guest users in the portal](add-users-administrator.md)
112-
- [Understand the invitation redemption process](redemption-experience.md)
112+
- [B2B direct connect](b2b-direct-connect-overview.md)

0 commit comments

Comments
 (0)