đź“‹ Microsoft Entra Documentation Changes

Daily summary for changes since April 16th 2026, 9:39 PM PDT

Report generated on April 17th 2026, 9:39 PM PDT

📊 Summary

32
Total Commits
0
New Files
20
Modified Files
0
Deleted Files
17
Contributors

📝 Modified Documentation Files

+22 / -21 lines changed
Commit: userstory538968
Changes:
Before
After
title: Regional opt-in for MFA telephony verification with external tenants (preview)
description: To protect customers, some regions require you to enable the country codes to receive SMS telephony verification for Microsoft Entra External ID external tenants.
ms.topic: how-to
ms.date: 11/12/2024
ms.reviewer: aloom3
ms.custom: it-pro, references_regions
 
#Customer intent: As a dev, devops, or it admin, I want to prevent telephony fraud by choosing which countries and regions to accept telecom traffic from.
---
 
# Regional opt-in for MFA telephony verification with external tenants (preview)
 
To safeguard against telephony fraud, Microsoft disallows traffic from certain phone number country codes. Doing so helps prevent unauthorized access and protect customers from fraudulent activities such as International Revenue Share Fraud (IRSF). With IRSF, criminals gain unauthorized access to a network and divert traffic to premium-rate numbers. They generate profits through a technique called traffic pumping. This technique often targets multifactor authentication systems, causing inflated charges, service instability, and system errors, making it harder for your customers to access your services.
 
When a country code is blocked, customers trying to set up SMS verification for multifactor authentication (MFA) for your application might encounter the message "Try another verification method." To resolve this issue, you can activate telephony traffic for the specific country code for your application.
 
You can use the Microsoft Graph API `onPhoneMethodLoadStart` event policy to manage telephony traffic for apps in your external tenant. With this event policy, you can activate or deactivate country codes for specific countries and regions.
 
[!INCLUDE [preview alert](includes/preview-alert/preview-alert-ciam.md)]
 
title: Regional opt-in for MFA telephony verification with external tenants (preview)
description: To protect customers, some regions require you to enable the country codes to receive SMS telephony verification for Microsoft Entra External ID external tenants.
ms.topic: how-to
ms.date: 04/17/2026
ms.reviewer: aloom3
ms.custom: it-pro, references_regions
ai-usage: ai-assisted
 
# Customer intent: As a dev, DevOps, or IT admin, I want to prevent telephony fraud by choosing which countries and regions to accept telephony traffic from.
---
 
# Regional opt-in for MFA telephony verification with external tenants (preview)
 
To safeguard against telephony fraud, Microsoft disallows traffic from certain phone number country codes. Doing so helps prevent unauthorized access and protect customers from fraudulent activities such as International Revenue Share Fraud (IRSF). With IRSF, criminals gain unauthorized access to a network and divert traffic to premium-rate numbers. They generate profits through a technique called traffic pumping. This technique often targets multifactor authentication systems, causing inflated charges, service instability, and system errors, making it harder for your customers to access your services.
 
When a country code is blocked, customers trying to set up SMS verification for multifactor authentication (MFA) for your application might encounter the message "Try another verification method." To resolve this issue, you can enable telephony traffic for specific country codes in your application.
 
You can use the Microsoft Graph API `onPhoneMethodLoadStart` event policy to manage telephony traffic for apps in your external tenant. With this event policy, you can enable or disable country codes for specific countries and regions.
 
[!INCLUDE [preview alert](includes/preview-alert/preview-alert-ciam.md)]
Modified by TheWriteDoc on Apr 17, 2026 9:20 PM
đź“– View on learn.microsoft.com
+21 / -19 lines changed
Commit: userstory538970
Changes:
Before
After
title: Set up AD FS federation
description: Learn how to set up SAML/WS-Fed IdP federation with AD FS for B2B collaboration in Microsoft Entra External ID. Configure AD FS as a SAML 2.0 or WS-Fed IdP and manage attributes and claims.
ms.topic: how-to
ms.date: 04/09/2025
ms.custom: "it-pro"
ms.collection: M365-identity-device-management
#customer intent: As an IT admin, I want to configure SAML/WS-Fed based identity provider federation with AD FS, so that I can enable federation between Microsoft Entra B2B and IdPs that use the SAML or WS-Fed protocol.
---
 
# Example: Set up SAML/WS-Fed IdP federation with AD FS for B2B collaboration
 
To set up federation, the following attributes must be received in the SAML 2.0 response from the IdP. These attributes can be configured by linking to the online security token service XML file or by entering them manually. Step 12 in [Create a test AD FS instance](https://medium.com/in-the-weeds/create-a-test-active-directory-federation-services-3-0-instance-on-an-azure-virtual-machine-9071d978e8ed) describes how to find the AD FS endpoints or how to generate your metadata URL, for example `https://fs.iga.azure-test.net/federationmetadata/2007-06/federationmetadata.xml`.
 
|Attribute |Value |
|---------|---------|
|AssertionConsumerService |`https://login.microsoftonline.com/login.srf` |
|Audience |`urn:federation:MicrosoftOnline` |
|Issuer |The issuer URI of the partner IdP, for example `http://www.example.com/exk10l6w90DHM0yi...` |
 
The following claims need to be configured in the SAML 2.0 token issued by the IdP:
title: Set up AD FS federation
description: Learn how to set up SAML/WS-Fed IdP federation with AD FS for B2B collaboration in Microsoft Entra External ID. Configure AD FS as a SAML 2.0 or WS-Fed IdP and manage attributes and claims.
ms.topic: how-to
ms.date: 04/17/2026
ms.custom: "it-pro"
ms.collection: M365-identity-device-management
ai-usage: ai-assisted
# Customer intent: As an IT admin, I want to configure SAML/WS-Fed-based identity provider federation with AD FS so that I can enable federation between Microsoft Entra B2B and IdPs that use the SAML or WS-Fed protocol.
---
 
# Example: Set up SAML/WS-Fed IdP federation with AD FS for B2B collaboration
 
To set up federation, the following attributes must be received in the SAML 2.0 response from the IdP. These attributes can be configured by linking to the online security token service XML file or by entering them manually. Step 12 in [Create a test AD FS instance](https://medium.com/in-the-weeds/create-a-test-active-directory-federation-services-3-0-instance-on-an-azure-virtual-machine-9071d978e8ed) describes how to find the AD FS endpoints or how to generate your metadata URL, for example `https://fs.iga.azure-test.net/federationmetadata/2007-06/federationmetadata.xml`.
 
| Attribute | Value |
| --- | --- |
| AssertionConsumerService | `https://login.microsoftonline.com/login.srf` |
| Audience | `urn:federation:MicrosoftOnline` |
| Issuer | The issuer URI of the partner IdP, for example `http://www.example.com/exk10l6w90DHM0yi...` |
 
+18 / -17 lines changed
Commit: userstory538969
Changes:
Before
After
title: Add MSA for customer sign-in
description: Learn how to add MSA as an identity provider for your external tenant.
ms.topic: how-to
ms.date: 09/16/2025
ms.custom: it-pro, has-azure-ad-ps-ref, azure-ad-ref-level-one-done
#Customer intent: As a dev, devops, or it admin, I want to
---
 
# Add Microsoft account (live.com) as an OpenID Connect identity provider
[!INCLUDE [applies-to-external-only](../includes/applies-to-external-only.md)]
 
By setting up federation with Microsoft account (live.com) using OpenID Connect (OIDC) identity provider, you enable users to sign up and sign in to your applications using their existing Microsoft accounts (MSA).
After you add the MSA (live.com) as one of your user flow's sign-in options, customers can sign up and sign in to your application with their Microsoft account.
 
## Prerequisites
 
- An [external tenant](how-to-create-external-tenant-portal.md).
- A [sign-up and sign-in user flow](how-to-user-flow-sign-up-sign-in-customers.md).
- A Microsoft account (live.com). If you don't already have one, sign up at https://www.live.com/.
 
title: Add MSA for customer sign-in
description: Learn how to add MSA as an identity provider for your external tenant.
ms.topic: how-to
ms.date: 04/17/2026
ms.custom: it-pro, has-azure-ad-ps-ref, azure-ad-ref-level-one-done
ai-usage: ai-assisted
# Customer intent: As a developer, DevOps engineer, or IT admin, I want to add Microsoft account as an identity provider so customers can sign in with their existing accounts.
---
 
# Add Microsoft account (live.com) as an OpenID Connect identity provider
[!INCLUDE [applies-to-external-only](../includes/applies-to-external-only.md)]
 
By setting up federation with Microsoft account (live.com) using OpenID Connect (OIDC) identity provider, you enable users to sign up and sign in to your applications using their existing Microsoft accounts (MSA).
After you add Microsoft account (live.com) as one of your user flow sign-in options, customers can sign up and sign in to your application by using their Microsoft account.
 
## Prerequisites
 
- An [external tenant](how-to-create-external-tenant-portal.md).
- A [sign-up and sign-in user flow](how-to-user-flow-sign-up-sign-in-customers.md).
- A Microsoft account (live.com). If you don't already have one, sign up at <https://www.live.com/>.
Modified by TheWriteDoc on Apr 17, 2026 8:30 PM
đź“– View on learn.microsoft.com
+15 / -10 lines changed
Commit: userstory538969
Changes:
Before
After
---
title: 'Quickstart: Add a guest user with PowerShell'
description: In this quickstart, you learn how to use PowerShell to send an invitation to a Microsoft Entra B2B collaboration user. You'll use the Microsoft Graph Identity Sign-ins and the Microsoft Graph Users PowerShell modules.
ms.date: 11/17/2025
ms.topic: quickstart
ms.custom: it-pro, mode-api, has-azure-ad-ps-ref, azure-ad-ref-level-one-done
ms.collection: M365-identity-device-management
#Customer intent: As an administrator, I want to add a guest user to my Microsoft Entra directory and send them an invitation via PowerShell, so that they can collaborate with my organization using their own work, school, or social account.
---
 
# Quickstart: Add a guest user with PowerShell
 
[!INCLUDE [applies-to-workforce-only](./includes/applies-to-workforce-only.md)]
 
There are many ways you can invite external partners to your apps and services with Microsoft Entra B2B collaboration. In the previous quickstart, you saw how to add guest users directly in the Microsoft Entra admin center. You can also use PowerShell to add guest users, either one at a time or in bulk. In this quickstart, you’ll use the New-MgInvitation command to add one guest user to your Microsoft Entra tenant.
 
This article explains how to invite guest users with Microsoft Graph PowerShell. You can also manage guest users with [Microsoft Entra PowerShell](/powershell/entra-powershell/manage-guest-users).
 
#Requires -Modules Microsoft.Graph.Identity.SignIns, Microsoft.Graph.Users
```
---
title: 'Quickstart: Add a guest user with PowerShell'
description: In this quickstart, you learn how to use PowerShell to send an invitation to a Microsoft Entra B2B collaboration user. You'll use the Microsoft Graph Identity Sign-ins and the Microsoft Graph Users PowerShell modules.
ms.date: 04/17/2026
ms.topic: quickstart
ms.custom: it-pro, mode-api, has-azure-ad-ps-ref, azure-ad-ref-level-one-done
ms.collection: M365-identity-device-management
ai-usage: ai-assisted
# Customer intent: As an administrator, I want to add a guest user to my Microsoft Entra directory and send them an invitation via PowerShell, so that they can collaborate with my organization by using their own work, school, or social account.
---
 
# Quickstart: Add a guest user with PowerShell
 
[!INCLUDE [applies-to-workforce-only](./includes/applies-to-workforce-only.md)]
 
There are many ways to invite external partners to your apps and services with Microsoft Entra B2B collaboration. In the previous quickstart, you saw how to add guest users directly in the Microsoft Entra admin center. You can also use PowerShell to add guest users, either one at a time or in bulk. In this quickstart, you use the `New-MgInvitation` command to add one guest user to your Microsoft Entra tenant.
 
This article explains how to invite guest users with Microsoft Graph PowerShell. You can also manage guest users with [Microsoft Entra PowerShell](/powershell/entra-powershell/manage-guest-users).
 
#Requires -Modules Microsoft.Graph.Identity.SignIns, Microsoft.Graph.Users
+13 / -12 lines changed
Commit: userstory538969
Changes:
Before
After
title: Set up claims mapping for OIDC
description: Learn how to configure the standard OpenID Connect claims with the claims your identity provider provides in your external tenant.
ms.topic: how-to
ms.date: 03/12/2025
ms.reviewer: brozbab
ms.custom: it-pro, sfi-image-nochange
#Customer intent: As a developer, devops, or it administrator, I want to learn how to configure the standard OpenID Connect claims with the claims my identity provider provides in my external tenant.
---
 
# OpenID Connect claims mapping
 
[!INCLUDE [applies-to-external-only](../includes/applies-to-external-only.md)]
 
In OpenID Connect protocol, claims are used to communicate information about the end user and contains pieces of information about a user that an identity provider states inside the ID token they issue for that user. The ID Token is a security token that contains claims about the end-user. These ID token claims are used to uniquely identify and provide information about the user during sign-up. These information pieces are stored in the corresponding user attributes in the user's profile in your directory.
 
To set up claims mapping, you need to create an identity provider (IdP) in your Microsoft Entra External ID tenant. The IdP configuration includes the **Claims mapping** section where you can configure the standard OpenID Connect (OIDC) claims with the claims your identity provider provides in the ID Token.
 
:::image type="content" source="media/reference-oidc-claims-mapping-customers/oidc-claims-mapping.png" alt-text="Screenshot of adding claims mapping.":::
 
## Claim and attribute mappings
title: Set up claims mapping for OIDC
description: Learn how to configure the standard OpenID Connect claims with the claims your identity provider provides in your external tenant.
ms.topic: how-to
ms.date: 04/17/2026
ms.reviewer: brozbab
ms.custom: it-pro, sfi-image-nochange
ai-usage: ai-assisted
# Customer intent: As a developer, DevOps, or IT administrator, I want to learn how to configure standard OpenID Connect claims with the claims that my identity provider provides in my external tenant.
---
 
# OpenID Connect claims mapping
 
[!INCLUDE [applies-to-external-only](../includes/applies-to-external-only.md)]
 
In the OpenID Connect protocol, claims communicate information about the end user. Claims are pieces of user information that an identity provider includes in the ID token it issues for that user. The ID token contains claims about the end user. During sign-up, these claims help uniquely identify the user and provide additional profile information. The values are stored in the corresponding user attributes in your directory.
 
To set up claims mapping, create an identity provider (IdP) in your Microsoft Entra External ID tenant. The IdP configuration includes the **Claims mapping** section, where you can map standard OpenID Connect (OIDC) claims to the claims your identity provider provides in the ID token.
 
:::image type="content" source="media/reference-oidc-claims-mapping-customers/oidc-claims-mapping.png" alt-text="Screenshot of the Configure OpenID Connect identity provider page in the Microsoft Entra admin center, highlighting the Claims mapping section.":::
 
+10 / -9 lines changed
Commit: userstory538970
Changes:
Before
After
title: Add Apple for customer sign-in
description: Learn how to add Apple as an identity provider for your external tenant.
ms.topic: how-to
ms.date: 04/10/2025
ms.custom: it-pro, sfi-image-nochange
#Customer intent: As a dev, devops, or it admin, I want to learn how to add Apple as an identity provider for my external tenant.
---
# Add Apple as an identity provider
 
[!INCLUDE [applies-to-external-only](../includes/applies-to-external-only.md)]
 
By setting up federation with Apple, you can allow customers to sign in to your applications with their own Apple accounts. After you've added Apple as one of your application's sign-in options, on the sign-in page, customers can sign-in to Microsoft Entra External ID with an Apple account. (Learn more about [authentication methods and identity providers for customers](concept-authentication-methods-customers.md).)
 
## Create an Apple application
 
To enable sign-in for customers with an Apple ID, you need to create an application in [Apple Developer panel](https://developer.apple.com/). If you don't already have an Apple ID, you can create one at Certificates, Identifiers & Profiles section.
 
> [!NOTE]
> This document was created using the state of the provider’s developer page at the time of creation, and changes may occur.
1. Browse to **Entra ID** > **External Identities** > **All identity providers**.
title: Add Apple for customer sign-in
description: Learn how to add Apple as an identity provider for your external tenant.
ms.topic: how-to
ms.date: 04/17/2026
ms.custom: it-pro, sfi-image-nochange
ai-usage: ai-assisted
# Customer intent: As a developer, DevOps engineer, or IT admin, I want to add Apple as an identity provider so customers can sign in with their Apple accounts.
---
# Add Apple as an identity provider
 
[!INCLUDE [applies-to-external-only](../includes/applies-to-external-only.md)]
 
By setting up federation with Apple, you can let customers sign in to your applications by using their own Apple accounts. After you add Apple as one of your application's sign-in options, customers can sign in to Microsoft Entra External ID with an Apple account. Learn more about [authentication methods and identity providers for customers](concept-authentication-methods-customers.md).
 
## Create an Apple application
 
To enable sign-in for customers with an Apple ID, you need to create an application in the [Apple Developer portal](https://developer.apple.com/). If you don't already have an Apple ID, you can create one in the **Certificates, IDs, & Profiles** section.
 
> [!NOTE]
> This document was created using the state of the provider’s developer page at the time of creation, and changes may occur.
Modified by TheWriteDoc on Apr 17, 2026 7:12 PM
đź“– View on learn.microsoft.com
+10 / -9 lines changed
Commit: userstory538968
Changes:
Before
After
title: Reset guest redemption status
description: Learn how to reset the redemption status for a guest user in Microsoft Entra External ID. This guide covers using the admin center, PowerShell, and Microsoft Graph API.
ms.topic: how-to
ms.date: 02/05/2025
ms.collection: M365-identity-device-management
ms.custom: sfi-image-nochange
# Customer intent: As an admin managing guest users in B2B collaboration, I want to reset the redemption status for a guest user, so that I can update their sign-in information and reinvite them without deleting their account.
---
 
- The user has moved to a different company, but they still need the same access to your resources
- The user’s responsibilities have been passed along to another user
 
To manage these scenarios previously, you had to manually delete the guest user’s account from your directory and reinvite the user. Now you can use the Microsoft Entra admin center, PowerShell, or the Microsoft Graph invitation API to reset the user's redemption status and reinvite the user while keeping the user's object ID, group memberships, and app assignments. When the user redeems the new invitation, the UserPrincipalName (UPN) of the user doesn't change, but the user's sign-in name changes to the new email. Then the user can sign in using the new email or an email you've added to the `otherMails` property of the user object.
 
<a name='required-azure-ad-roles'></a>
 
 
1. On the **Overview** tab, under **My Feed**, select the **Reset redemption status** link in the **B2B collaboration** tile.
 
:::image type="content" source="media/reset-redemption-status/user-profile-b2b-collaboration.png" alt-text="Screenshot showing the B2B collaboration reset link." lightbox="media/reset-redemption-status/user-profile-b2b-collaboration.png":::
title: Reset guest redemption status
description: Learn how to reset the redemption status for a guest user in Microsoft Entra External ID. This guide covers using the admin center, PowerShell, and Microsoft Graph API.
ms.topic: how-to
ms.date: 04/17/2026
ms.collection: M365-identity-device-management
ms.custom: sfi-image-nochange
ai-usage: ai-assisted
# Customer intent: As an admin managing guest users in B2B collaboration, I want to reset the redemption status for a guest user, so that I can update their sign-in information and reinvite them without deleting their account.
---
 
- The user has moved to a different company, but they still need the same access to your resources
- The user’s responsibilities have been passed along to another user
 
In the past, to manage these scenarios, you had to manually delete the guest user's account from your directory and reinvite the user. Now you can use the Microsoft Entra admin center, PowerShell, or the Microsoft Graph invitation API to reset the user's redemption status and reinvite the user while keeping the user's object ID, group memberships, and app assignments. When the user redeems the new invitation, the user principal name (UPN) doesn't change, but the user's sign-in name changes to the new email. The user can then sign in by using the new email or an email you've added to the `otherMails` property of the user object.
 
<a name='required-azure-ad-roles'></a>
 
 
1. On the **Overview** tab, under **My Feed**, select the **Reset redemption status** link in the **B2B collaboration** tile.
 
Modified by TheWriteDoc on Apr 17, 2026 9:20 PM
đź“– View on learn.microsoft.com
+9 / -8 lines changed
Commit: userstory538970
Changes:
Before
After
title: Add Facebook as an identity provider
description: Federate with Facebook to enable external users (guests) to sign in to your Microsoft Entra apps with their own Facebook accounts.
ms.topic: how-to
ms.date: 07/07/2025
ms.collection: M365-identity-device-management
ms.custom: it-pro, has-azure-ad-ps-ref, azure-ad-ref-level-one-done, sfi-ga-nochange, sfi-image-nochange
#customer intent: As a B2B collaboration administrator, I want to add Facebook as an identity provider for self-service sign-up user flows, so that users can sign in to applications using their Facebook accounts.
---
 
# Add Facebook as an identity provider for External ID
 
You can add Facebook to your self-service sign-up user flows so that users can sign in to your applications using their own Facebook accounts. To allow users to sign in using Facebook, you first need to [enable self-service sign-up](self-service-sign-up-user-flow.yml) for your tenant. After you add Facebook as an identity provider, set up a user flow for the application and select Facebook as one of the sign-in options.
 
After you add Facebook as one of your application's sign-in options, on the **Sign in** page, a user can enter the email they use to sign in to Facebook, or they can select **Sign-in options** and choose **Sign in with Facebook**. In either case, they're redirected to the Facebook sign in page for authentication.
 
![Sign in options for facebook users](media/facebook-federation/sign-in-with-facebook-overview.png)
 
> [!NOTE]
> Users can only use their Facebook accounts to sign up through apps using self-service sign-up and user flows. Users can't be invited and redeem their invitation using a Facebook account.
1. Select **App settings** > **Basic**.
title: Add Facebook as an identity provider
description: Federate with Facebook to enable external users (guests) to sign in to your Microsoft Entra apps with their own Facebook accounts.
ms.topic: how-to
ms.date: 04/17/2026
ms.collection: M365-identity-device-management
ms.custom: it-pro, has-azure-ad-ps-ref, azure-ad-ref-level-one-done, sfi-ga-nochange, sfi-image-nochange
ai-usage: ai-assisted
# Customer intent: As a B2B collaboration administrator, I want to add Facebook as an identity provider for self-service sign-up user flows so users can sign in to applications by using their Facebook accounts.
---
 
# Add Facebook as an identity provider for External ID
 
You can add Facebook to your self-service sign-up user flows so that users can sign in to your applications using their own Facebook accounts. To allow users to sign in using Facebook, you first need to [enable self-service sign-up](self-service-sign-up-user-flow.yml) for your tenant. After you add Facebook as an identity provider, set up a user flow for the application and select Facebook as one of the sign-in options.
 
After you add Facebook as one of your application's sign-in options, on the **Sign in** page a user can enter the email they use for Facebook. Or they can select **Sign-in options** and choose **Sign in with Facebook**. In either case, they're redirected to the Facebook sign-in page for authentication.
 
![Screenshot of a Microsoft Entra External ID sign-in page showing Sign-in options and the Sign in with Facebook option.](media/facebook-federation/sign-in-with-facebook-overview.png)
 
> [!NOTE]
> Users can only use their Facebook accounts to sign up through apps using self-service sign-up and user flows. Users can't be invited and redeem their invitation using a Facebook account.
Modified by TheWriteDoc on Apr 17, 2026 9:20 PM
đź“– View on learn.microsoft.com
+9 / -8 lines changed
Commit: userstory538970
Changes:
Before
After
---
title: Invite internal users to B2B collaboration
description: If you have internal user accounts for partners, distributors, suppliers, vendors, and other guests, you can change to Microsoft Entra B2B collaboration by inviting them to sign in with their own external credentials or sign-in. Use either PowerShell or the Microsoft Graph invitation API.
ms.topic: how-to
ms.date: 02/25/2025
ms.collection: M365-identity-device-management
ms.custom: has-azure-ad-ps-ref, azure-ad-ref-level-one-done, sfi-image-nochange
# Customer intent: As an IT admin managing internal guest users, I want to invite them to use B2B collaboration, so that they can sign in using their own identities and credentials, eliminating the need for password maintenance or account lifecycle management.
---
 
 
Before the availability of Microsoft Entra B2B collaboration, organizations could collaborate with distributors, suppliers, vendors, and other guest users by setting up internal credentials for them. If you have internal guest users like these, you can invite them to use B2B collaboration instead. These B2B guest users are able to sign in using their own identities and credentials, eliminating the need for password maintenance or account lifecycle management.
 
Sending an invitation to an existing internal account lets you retain that user’s object ID, User Principal Name (UPN), group memberships, and app assignments. You don’t need to manually delete and reinvite the user or reassign resources. To invite the user, you use the invitation API to pass both the internal user object and the guest user’s email address along with the invitation. When the user accepts the invitation, the B2B service changes the existing internal user object to a B2B user. Going forward, the user must sign in to cloud resources services using their B2B credentials.
 
## Things to consider
 
1. Find the user in the list or use the search box. Then select the user.
1. In the **Overview** tab, under **My Feed**, select **Convert to external user**.
 
---
title: Invite internal users to B2B collaboration
description: If you have internal user accounts for partners, distributors, suppliers, vendors, and other guests, you can move to Microsoft Entra B2B collaboration by inviting them to sign in with their own external credentials. Use either PowerShell or the Microsoft Graph invitation API.
ms.topic: how-to
ms.date: 04/17/2026
ms.collection: M365-identity-device-management
ms.custom: has-azure-ad-ps-ref, azure-ad-ref-level-one-done, sfi-image-nochange
ai-usage: ai-assisted
# Customer intent: As an IT admin managing internal guest users, I want to invite them to use B2B collaboration, so that they can sign in using their own identities and credentials, eliminating the need for password maintenance or account lifecycle management.
---
 
 
Before the availability of Microsoft Entra B2B collaboration, organizations could collaborate with distributors, suppliers, vendors, and other guest users by setting up internal credentials for them. If you have internal guest users like these, you can invite them to use B2B collaboration instead. These B2B guest users are able to sign in using their own identities and credentials, eliminating the need for password maintenance or account lifecycle management.
 
Sending an invitation to an existing internal account lets you retain that user's object ID, user principal name (UPN), group memberships, and app assignments. You don't need to manually delete and reinvite the user or reassign resources. To invite the user, you use the invitation API to pass both the internal user object and the guest user's email address along with the invitation. When the user accepts the invitation, the B2B service changes the existing internal user object to a B2B user. Going forward, the user must sign in to cloud resource services by using B2B credentials.
 
## Things to consider
 
1. Find the user in the list or use the search box. Then select the user.
1. In the **Overview** tab, under **My Feed**, select **Convert to external user**.
+9 / -8 lines changed
Commit: userstory538968
Changes:
Before
After
title: Using role-based access control for apps
description: Learn how to define application roles for your consumer and business customer applications and assign those roles to users and groups in external tenants.
ms.topic: how-to
ms.date: 09/16/2025
ms.custom: it-pro, sfi-ga-nochange
---
 
# Using role-based access control for applications
 
Role-based access control (RBAC) is a popular mechanism to enforce authorization in applications. When an organization uses RBAC, an application developer defines roles for the application. An administrator can then assign roles to different users and groups to control who has access to content and functionality in the application.
 
Applications typically receive user role information as claims in a security token. Developers have the flexibility to provide their own implementation for how role claims are to be interpreted as application permissions. This interpretation of permissions can involve using middleware or other options provided by the platform of the applications or related libraries.
 
## App roles
 
 
Though you can use app roles or groups for authorization, key differences between them can influence which you decide to use for your scenario.
 
| App roles| Groups|
| ----- | ----- |
title: Using role-based access control for apps
description: Learn how to define application roles for your consumer and business customer applications and assign those roles to users and groups in external tenants.
ms.topic: how-to
ms.date: 04/17/2026
ms.custom: it-pro, sfi-ga-nochange
ai-usage: ai-assisted
---
 
# Using role-based access control for applications
 
Role-based access control (RBAC) is a popular mechanism to enforce authorization in applications. When an organization uses RBAC, an application developer defines roles for the application. An administrator can then assign roles to different users and groups to control who has access to content and functionality in the application.
 
Applications typically receive user role information as claims in a security token. Developers can provide their own implementation for how role claims are interpreted as application permissions. This interpretation can involve using middleware or other options provided by the application platform or related libraries.
 
## App roles
 
 
Though you can use app roles or groups for authorization, key differences between them can influence which you decide to use for your scenario.
 
| App roles | Groups |
+8 / -8 lines changed
Commit: Remove preview label from cloud firewall with remote networks (GA) - AB#570422
Changes:
Before
After
---
title: Configure Global Secure Access cloud firewall with remote networks for internet access
description: Learn how to configure and use GSA Cloud Firewall to protect against unauthorized internet access from branch offices using Remote Networks for Internet Access.
author: jenniferf-skc
ms.author: jfields
ms.topic: how-to
ms.subservice: entra-private-access
ms.date: 11/18/2025
ms.custom: it-pro
ms.reviewer: shkhalid
ai-usage: ai-assisted
 
#customer intent: As a Global Secure Access administrator, I want to learn how to configure and use GSA Cloud Firewall to protect against unauthorized internet access from branch offices using Remote Networks for Internet Access.
---
 
# Configure Global Secure Access cloud firewall (preview)
 
Global Secure Access (GSA) Cloud Firewall (CFW) protects customers from unauthorized egress access by applying policies on network traffic. Cloud firewall provides centralized management, visibility, and consistent policies for branches.
 
The current scope of this preview is using GSA Cloud Firewall to enforce policies on Internet traffic from branch offices using Remote Networks for Internet Access (also in preview).
---
title: Configure Global Secure Access cloud firewall with remote networks for internet access
description: Learn how to configure and use cloud firewall to protect against unauthorized internet access from branch offices using Remote Networks for Internet Access.
author: jenniferf-skc
ms.author: jfields
ms.topic: how-to
ms.subservice: entra-private-access
ms.date: 04/17/2026
ms.custom: it-pro
ms.reviewer: shkhalid
ai-usage: ai-assisted
 
#customer intent: As a Global Secure Access administrator, I want to learn how to configure and use cloud firewall to protect against unauthorized internet access from branch offices using Remote Networks for Internet Access.
---
 
# Configure Global Secure Access cloud firewall
 
Global Secure Access Cloud Firewall (CFW) protects customers from unauthorized egress access by applying policies on network traffic. Cloud firewall provides centralized management, visibility, and consistent policies for branches.
 
The current scope is using cloud firewall to enforce policies on Internet traffic from branch offices using Remote Networks for Internet Access.
Modified by TheWriteDoc on Apr 17, 2026 9:20 PM
đź“– View on learn.microsoft.com
+7 / -5 lines changed
Commit: userstory538970
Changes:
Before
After
title: About API connectors in self-service sign-up flows
description: Use Microsoft Entra API connectors to customize and extend your self-service sign-up user flows by using web APIs.
ms.topic: concept-article
ms.date: 04/14/2025
ms.custom: "it-pro"
ms.collection: M365-identity-device-management
#customer intent: As a developer or IT administrator, I want to use API connectors to customize and extend the self-service sign-up user flows, so that I can integrate with web APIs, customize the sign-up experience, and integrate with external systems for tasks such as approval workflows, identity verification, data validation, attribute manipulation, and running custom business logic.
---
 
# Use API connectors to customize and extend self-service sign-up
 
[!INCLUDE [applies-to-workforce-only](./includes/applies-to-workforce-only.md)]
 
## Overview
As a developer or IT administrator, you can use [API connectors](self-service-sign-up-add-api-connector.md#create-an-api-connector) to integrate your [self-service sign-up user flows](self-service-sign-up-overview.md) with web APIs to customize the sign-up experience and integrate with external systems. For example, with API connectors, you can:
 
- [**Integrate with a custom approval workflow**](self-service-sign-up-add-approvals.md). Connect to a custom approval system for managing and limiting account creation.
- **Overwrite user attributes**. Reformat or assign a value to an attribute collected from the user. For example, if a user enters the first name in all lowercase or all uppercase letters, you can format the name with only the first letter capitalized.
- **Run custom business logic**. You can trigger downstream events in your cloud systems to send push notifications, update corporate databases, manage permissions, audit databases, and perform other custom actions.
 
title: About API connectors in self-service sign-up flows
description: Use Microsoft Entra API connectors to customize and extend your self-service sign-up user flows by using web APIs.
ms.topic: concept-article
ms.date: 04/17/2026
ms.custom: "it-pro"
ms.collection: M365-identity-device-management
ai-usage: ai-assisted
# Customer intent: As a developer or IT administrator, I want to use API connectors to customize and extend self-service sign-up user flows so that I can integrate with web APIs and external systems for tasks such as approval workflows, identity verification, data validation, attribute manipulation, and custom business logic.
---
 
# Use API connectors to customize and extend self-service sign-up
 
[!INCLUDE [applies-to-workforce-only](./includes/applies-to-workforce-only.md)]
 
## Overview
As a developer or IT administrator, you can use [API connectors](self-service-sign-up-add-api-connector.md#create-an-api-connector) to integrate your [self-service sign-up user flows](self-service-sign-up-overview.md) with web APIs to customize the sign-up experience and integrate with external systems. For example, with API connectors, you can:
 
- [**Integrate with a custom approval workflow**](self-service-sign-up-add-approvals.md). Connect to a custom approval system for managing and limiting account creation.
- **Overwrite user attributes**. Reformat or assign a value to an attribute collected from the user. For example, if a user enters the first name in all lowercase or all uppercase letters, you can format the name with only the first letter capitalized.
- **Run custom business logic**. You can trigger downstream events in your cloud systems to send push notifications, update corporate databases, manage permissions, audit databases, and perform other custom actions.
Modified by TheWriteDoc on Apr 17, 2026 8:30 PM
đź“– View on learn.microsoft.com
+6 / -5 lines changed
Commit: userstory538969
Changes:
Before
After
title: Add custom attributes
description: Learn how to add custom attributes to self-service sign-up flows in Microsoft Entra External ID. Extend the set of attributes stored on a guest account and customize the user experience.
ms.topic: how-to
ms.date: 10/06/2025
ms.custom: it-pro
ms.collection: M365-identity-device-management
 
#customer intent: As a B2B collaboration user flow administrator, I want to define custom attributes for user flows in Microsoft Entra, so that I can collect specific information during sign-up and extend the set of attributes stored on a guest account.
---
 
# Collect custom user attributes during B2B collaboration sign-up
 
 
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [User Administrator](~/identity/role-based-access-control/permissions-reference.md#user-administrator).
1. Browse to **Entra ID** > **External Identities** > **Overview**.
1. Select **Custom user attributes**. The available user attributes are listed.
 
:::image type="content" source="media/user-flow-add-custom-attributes/user-attributes.png" alt-text="Screenshot of selecting custom user attributes for sign-up." lightbox="media/user-flow-add-custom-attributes/user-attributes.png":::
 
 
title: Add custom attributes
description: Learn how to add custom attributes to self-service sign-up flows in Microsoft Entra External ID. Extend the set of attributes stored on a guest account and customize the user experience.
ms.topic: how-to
ms.date: 04/17/2026
ms.custom: it-pro
ms.collection: M365-identity-device-management
ai-usage: ai-assisted
 
# Customer intent: As a B2B collaboration user flow administrator, I want to define custom attributes for user flows in Microsoft Entra, so that I can collect specific information during sign-up and extend the set of attributes stored on a guest account.
---
 
# Collect custom user attributes during B2B collaboration sign-up
 
 
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [User Administrator](~/identity/role-based-access-control/permissions-reference.md#user-administrator).
1. Browse to **Entra ID** > **External identities** > **Overview**.
1. Select **Custom user attributes**. The available user attributes are listed.
 
:::image type="content" source="media/user-flow-add-custom-attributes/user-attributes.png" alt-text="Screenshot of the External identities overview page in the Microsoft Entra admin center, with Custom user attributes selected." lightbox="media/user-flow-add-custom-attributes/user-attributes.png":::
 
Modified by John Flores on Apr 17, 2026 2:36 PM
đź“– View on learn.microsoft.com
+5 / -5 lines changed
Commit: [ZT Assessment] Customer feedback issue 1161
Changes:
Before
After
---
title: Admin consent workflow is enabled
ms.author: barclayn
author: barclayn
manager: pmwongera
ms.service: entra-id
ms.topic: include
ms.date: 04/27/2025
ms.custom: Identity-Secure-Recommendation
# minimumlicense: Free
# sfipillar: Protect identities and secrets
# userimpact: Low
# implementationcost: Low
---
Enabling the Admin consent workflow in a Microsoft Entra tenant is a vital security measure that mitigates risks associated with unauthorized application access and privilege escalation. This check is important because it ensures that any application requesting elevated permission undergoes a review process by designated administrators before consent is granted. The admin consent workflow in Microsoft Entra ID notifies reviewers who evaluate and approve or deny consent requests based on the application's legitimacy and necessity. If this check doesn't pass, meaning the workflow is disabled, any application can request and potentially receive elevated permissions without administrative review. This poses a substantial security risk, as malicious actors could exploit this lack of oversight to gain unauthorized access to sensitive data, perform privilege escalation, or execute other malicious activities.
 
**Remediation action**
 
---
title: Admin consent workflow is enabled
ms.author: joflore
author: MicrosoftGuyJFlo
manager: CelesteDG
ms.service: entra-id
ms.topic: include
ms.date: 04/17/2026
ms.custom: Identity-Secure-Recommendation
# minimumlicense: Free
# sfipillar: Protect identities and secrets
# userimpact: Low
# implementationcost: Low
---
Enabling the admin consent workflow in a Microsoft Entra tenant ensures that users who need access to an application that requires admin consent can submit a request for review rather than being blocked outright. Without the workflow, users who can't consent to an app on their own may resort to shadow IT workarounds, such as using personal accounts or unsanctioned alternatives—that are harder to monitor and secure. When the workflow is enabled, consent requests go through a logged, auditable process where designated reviewers are notified and evaluate each request before consent is granted. This improves observability into which applications users are requesting access to, and ensures that elevated permissions are reviewed and explicitly approved rather than silently blocked or granted without oversight.
 
**Remediation action**
 
+5 / -4 lines changed
Commit: userstory538968
Changes:
Before
After
title: Add and manage admin accounts
description: Learn how to add and manage admin accounts in your external tenant with Microsoft Entra External ID.
ms.topic: how-to
ms.date: 03/10/2025
ms.custom: it-pro
 
---
# Add and manage admin accounts
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Privileged Role Administrator](/entra/identity/role-based-access-control/permissions-reference#privileged-role-administrator).
1. If you have access to multiple tenants, use the **Settings** icon :::image type="icon" source="media/common/admin-center-settings-icon.png" border="false"::: in the top menu to switch to your external tenant from the **Directories + subscriptions** menu.
1. Browse to **Entra ID** > **Roles & admins**.
2. Select a role, such as **User Administrator**. The **Assignments** page lists the users with that role.
 
## Delete an administrator account
 
To delete an existing user, you must have at least the [User Administrator](/entra/identity/role-based-access-control/permissions-reference#user-administrator) role assignment. [Privileged Authentication Administrators](/entra/identity/role-based-access-control/permissions-reference#privileged-authentication-administrator) can delete any user, including other admins. *User Administrators* can delete any non-admin user.
 
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Privileged Authentication Administrators](/entra/identity/role-based-access-control/permissions-reference#privileged-authentication-administrator).
1. If you have access to multiple tenants, use the **Settings** icon :::image type="icon" source="media/common/admin-center-settings-icon.png" border="false"::: in the top menu to switch to your external tenant from the **Directories + subscriptions** menu.
1. Browse to **Entra ID** > **Users**.
title: Add and manage admin accounts
description: Learn how to add and manage admin accounts in your external tenant with Microsoft Entra External ID.
ms.topic: how-to
ms.date: 04/17/2026
ms.custom: it-pro
ai-usage: ai-assisted
 
---
# Add and manage admin accounts
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Privileged Role Administrator](/entra/identity/role-based-access-control/permissions-reference#privileged-role-administrator).
1. If you have access to multiple tenants, use the **Settings** icon :::image type="icon" source="media/common/admin-center-settings-icon.png" border="false"::: in the top menu to switch to your external tenant from the **Directories + subscriptions** menu.
1. Browse to **Entra ID** > **Roles & admins**.
1. Select a role, such as **User Administrator**. The **Assignments** page lists the users with that role.
 
## Delete an administrator account
 
To delete an existing user, you must have at least the [User Administrator](/entra/identity/role-based-access-control/permissions-reference#user-administrator) role assignment. [Privileged Authentication Administrators](/entra/identity/role-based-access-control/permissions-reference#privileged-authentication-administrator) can delete any user, including other admins. *User Administrators* can delete any non-admin user.
 
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Privileged Authentication Administrator](/entra/identity/role-based-access-control/permissions-reference#privileged-authentication-administrator).
1. If you have access to multiple tenants, use the **Settings** icon :::image type="icon" source="media/common/admin-center-settings-icon.png" border="false"::: in the top menu to switch to your external tenant from the **Directories + subscriptions** menu.