Skip to content

Commit ba36d80

Browse files
authored
Merge pull request #239029 from MicrosoftDocs/main
5/23 PM Publish
2 parents 4549c44 + 14b3c4b commit ba36d80

File tree

418 files changed

+7761
-3118
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

418 files changed

+7761
-3118
lines changed

.openpublishing.redirection.json

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22758,6 +22758,26 @@
2275822758
"source_path_from_root": "/articles/azure-functions/functions-create-function-linux-custom-image.md",
2275922759
"redirect_url": "/azure/azure-functions/functions-how-to-custom-container",
2276022760
"redirect_document_id": false
22761+
},
22762+
{
22763+
"source_path_from_root": "/articles/sentinel/data-connectors/windows-firewall-events-via-ama.md",
22764+
"redirect_url": "/azure/sentinel/data-connectors-reference",
22765+
"redirect_document_id": false
22766+
},
22767+
{
22768+
"source_path_from_root": "/articles/sentinel/data-connectors/cisco-meraki.md",
22769+
"redirect_url": "/azure/sentinel/data-connectors-reference",
22770+
"redirect_document_id": false
22771+
},
22772+
{
22773+
"source_path_from_root": "/articles/sentinel/data-connectors/cisco-asa-ftd-via-ama.md",
22774+
"redirect_url": "/azure/sentinel/data-connectors-reference",
22775+
"redirect_document_id": false
22776+
},
22777+
{
22778+
"source_path_from_root": "/articles/sentinel/data-connectors/threat-intelligence-upload-indicators-api.md",
22779+
"redirect_url": "/azure/sentinel/data-connectors-reference",
22780+
"redirect_document_id": false
2276122781
}
2276222782
]
2276322783
}

articles/active-directory-b2c/faq.yml

Lines changed: 16 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ metadata:
88
ms.service: active-directory
99
ms.workload: identity
1010
ms.topic: faq
11-
ms.date: 03/15/2023
11+
ms.date: 05/23/2023
1212
ms.author: godonnell
1313
ms.subservice: B2C
1414
ms.custom: "b2c-support"
@@ -17,6 +17,20 @@ summary: This page answers frequently asked questions about the Azure Active Dir
1717

1818

1919
sections:
20+
- name: Microsoft Entra External ID preview
21+
questions:
22+
- question: |
23+
What is Microsoft Entra External ID?
24+
answer: |
25+
We announced early preview of our next generation Microsoft Entra External ID solution. This early preview represents an evolutionary step in unifying secure and engaging experiences across all external identities including partners, customers, citizens, patients, and others within a single, integrated platform. For more information about the preview, see [What is Microsoft Entra External ID for customers?](../active-directory/external-identities/customers/overview-customers-ciam.md).
26+
- question: |
27+
How does this preview affect me?
28+
answer: |
29+
No action is required on your part at this time. The next generation platform is currently in early preview only. We remain fully committed to support of your current Azure AD B2C solution. There are no requirements for Azure AD B2C customers to migrate at this time and no plans to discontinue the current Azure AD B2C service. As the next generation platform approaches GA, details will be made available to all our valued B2C customers on available options including migration to the new platform.
30+
- question: |
31+
How do I participate in the preview?
32+
answer: |
33+
As the next generation platform represents our future for customer identity and access management (CIAM), we welcome and encourage your participation and feedback during early preview. If you're interested in joining the early preview, contact your sales team for details.
2034
- name: General
2135
questions:
2236
- question: |
@@ -164,7 +178,7 @@ sections:
164178
If the TOTP authenticator app codes aren't working with your Android or iPhone mobile phone or device, your device's clock time might be incorrect. In your device's settings, select the option to use the network-provided time or to set the time automatically.
165179
166180
- question: |
167-
How do I know that the Go-Local add-on available in my country/region?
181+
How do I know that the Go-Local add-on is available in my country/region?
168182
answer: |
169183
While [creating your Azure AD B2C tenant](tutorial-create-tenant.md), if the Go-Local add-on is available in your country, you're asked to enable it if you need it.
170184

articles/active-directory/authentication/how-to-migrate-mfa-server-to-mfa-user-authentication.md

Lines changed: 16 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -1,25 +1,20 @@
11
---
22
title: Migrate to Azure AD MFA and Azure AD user authentication
3-
description: Step-by-step guidance to move from MFA Server on-premises to Azure AD MFA and Azure AD user authentication
4-
3+
description: Guidance to move from MFA Server on-premises to Azure AD MFA and Azure AD user authentication
54
services: multi-factor-authentication
65
ms.service: active-directory
76
ms.subservice: authentication
87
ms.topic: how-to
9-
ms.date: 01/29/2023
10-
8+
ms.date: 05/23/2023
119
ms.author: gasinh
1210
author: gargi-sinha
1311
manager: martinco
1412
ms.reviewer: michmcla
15-
1613
ms.collection: M365-identity-device-management
1714
---
1815
# Migrate to Azure AD MFA and Azure AD user authentication
1916

20-
Multi-factor authentication (MFA) helps secure your infrastructure and assets from bad actors.
21-
Microsoft's Multi-Factor Authentication Server (MFA Server) is no longer offered for new deployments.
22-
Customers who are using MFA Server should move to Azure AD Multi-Factor Authentication (Azure AD MFA).
17+
Multi-factor authentication (MFA) helps secure your infrastructure and assets from bad actors. Microsoft Multi-Factor Authentication Server (MFA Server) is no longer offered for new deployments. Customers who are using MFA Server should move to Azure AD Multi-Factor Authentication (Azure AD MFA).
2318

2419
There are several options for migrating from MFA Server to Azure Active Directory (Azure AD):
2520

@@ -66,7 +61,7 @@ Groups are used in three capacities for MFA migration.
6661
### Configure Conditional Access policies
6762

6863
If you're already using Conditional Access to determine when users are prompted for MFA, you won't need any changes to your policies.
69-
As users are migrated to cloud authentication, they'll start using Azure AD MFA as defined by your existing Conditional Access policies.
64+
As users are migrated to cloud authentication, they'll start using Azure AD MFA as defined by your Conditional Access policies.
7065
They won't be redirected to AD FS and MFA Server anymore.
7166

7267
If your federated domains have the **federatedIdpMfaBehavior** set to `enforceMfaByFederatedIdp` or **SupportsMfa** flag set to `$True` (the **federatedIdpMfaBehavior** overrides **SupportsMfa** when both are set), you're likely enforcing MFA on AD FS by using claims rules.
@@ -98,20 +93,20 @@ Now that Azure AD MFA is an additional authentication method, you can assign gro
9893
>[!NOTE]
9994
>Claims rules require on-premises security group.
10095
101-
#### Back up existing rules
96+
#### Back up rules
10297

103-
Before configuring new claims rules, back up your existing rules.
104-
You'll need to restore claims rules as a part of your cleanup steps.
98+
Before configuring new claims rules, back up your rules.
99+
You'll need to restore claims rules as a part of your clean-up steps.
105100

106101
Depending on your configuration, you may also need to copy the existing rule and append the new rules being created for the migration.
107102

108-
To view existing global rules, run:
103+
To view global rules, run:
109104

110105
```powershell
111106
Get-AdfsAdditionalAuthenticationRule
112107
```
113108

114-
To view existing relying party trusts, run the following command and replace RPTrustName with the name of the relying party trust claims rule:
109+
To view relying party trusts, run the following command and replace RPTrustName with the name of the relying party trust claims rule:
115110

116111
```powershell
117112
(Get-AdfsRelyingPartyTrust -Name "RPTrustName").AdditionalAuthenticationRules
@@ -139,17 +134,17 @@ To find the group SID, run the following command and replace `GroupName` with yo
139134
Get-ADGroup GroupName
140135
```
141136

142-
![PowerShell command to get the group SID.](media/how-to-migrate-mfa-server-to-mfa-user-authentication/find-the-sid.png)
137+
![Microsoft Graph PowerShell command to get the group SID.](media/how-to-migrate-mfa-server-to-mfa-user-authentication/find-the-sid.png)
143138

144139
#### Setting the claims rules to call Azure AD MFA
145140

146-
The following PowerShell cmdlets invoke Azure AD MFA for users in the group when they aren't on the corporate network.
147-
You must replace `"YourGroupSid"` with the SID found by running the preceding cmdlet.
141+
The following Microsoft Graph PowerShell cmdlets invoke Azure AD MFA for users in the group when they aren't on the corporate network.
142+
Replace `"YourGroupSid"` with the SID found by running the preceding cmdlet.
148143

149144
Make sure you review the [How to Choose Additional Auth Providers in 2019](/windows-server/identity/ad-fs/overview/whats-new-active-directory-federation-services-windows-server#how-to-choose-additional-auth-providers-in-2019).
150145

151146
>[!IMPORTANT]
152-
>Backup your existing claims rules before proceeding.
147+
>Back up your claims rules before proceeding.
153148
154149
##### Set global claims rule
155150

@@ -209,8 +204,7 @@ Value=="YourGroupSid"]) => issue(Type =
209204

210205
### Configure Azure AD MFA as an authentication provider in AD FS
211206

212-
In order to configure Azure AD MFA for AD FS, you must configure each AD FS server.
213-
If multiple AD FS servers are in your farm, you can configure them remotely using Azure AD PowerShell.
207+
In order to configure Azure AD MFA for AD FS, you must configure each AD FS server. If multiple AD FS servers are in your farm, you can configure them remotely using Microsoft Graph PowerShell.
214208

215209
For step-by-step directions on this process, see [Configure the AD FS servers](/windows-server/identity/ad-fs/operations/configure-ad-fs-and-azure-mfa#configure-the-ad-fs-servers).
216210

@@ -340,7 +334,7 @@ Possible considerations when decommissions the MFA Server include:
340334

341335
## Move application authentication to Azure Active Directory
342336

343-
If you migrate all your application authentication along with your MFA and user authentication, you'll be able to remove significant portions of your on-premises infrastructure, reducing costs and risks.
337+
If you migrate all your application authentication with your MFA and user authentication, you'll be able to remove significant portions of your on-premises infrastructure, reducing costs and risks.
344338
If you move all application authentication, you can skip the [Prepare AD FS](#prepare-ad-fs) stage and simplify your MFA migration.
345339

346340
The process for moving all application authentication is shown in the following diagram.
@@ -353,5 +347,5 @@ For more information about migrating applications to Azure, see [Resources for m
353347
## Next steps
354348

355349
- [Migrate from Microsoft MFA Server to Azure AD MFA (Overview)](how-to-migrate-mfa-server-to-azure-mfa.md)
356-
- [Migrate applications from Windows Active Directory to Azure Active Directory](../manage-apps/migrate-application-authentication-to-azure-active-directory.md)
350+
- [Migrate applications from Windows Active Directory to Azure AD](../manage-apps/migrate-application-authentication-to-azure-active-directory.md)
357351
- [Plan your cloud authentication strategy](../fundamentals/active-directory-deployment-plans.md)

articles/active-directory/develop/custom-extension-get-started.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.service: active-directory
1010
ms.subservice: develop
1111
ms.topic: how-to
1212
ms.workload: identity
13-
ms.date: 04/10/2023
13+
ms.date: 05/23/2023
1414
ms.author: davidmu
1515
ms.custom: aaddev
1616
ms.reviewer: JasSuri
@@ -128,7 +128,7 @@ The following screenshot demonstrates how to configure the Azure HTTP trigger fu
128128
public Claims claims { get; set; }
129129
public Action()
130130
{
131-
odatatype = "microsoft.graph.provideClaimsForToken";
131+
odatatype = "microsoft.graph.tokenIssuanceStart.provideClaimsForToken";
132132
claims = new Claims();
133133
}
134134
}

articles/active-directory/devices/azuread-join-sso.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -42,6 +42,8 @@ Azure AD Connect or Azure AD Connect cloud sync synchronize your on-premises ide
4242
> Additional configuration is required when passwordless authentication to Azure AD joined devices is used.
4343
>
4444
> For FIDO2 security key based passwordless authentication and Windows Hello for Business Hybrid Cloud Trust, see [Enable passwordless security key sign-in to on-premises resources with Azure Active Directory](../authentication/howto-authentication-passwordless-security-key-on-premises.md).
45+
>
46+
> For Windows Hello for Business Cloud Kerberos Trust, see [Configure and provision Windows Hello for Business - cloud Kerberos trust](/windows/security/identity-protection/hello-for-business/hello-hybrid-cloud-kerberos-trust-provision).
4547
>
4648
> For Windows Hello for Business Hybrid Key Trust, see [Configure Azure AD joined devices for On-premises Single-Sign On using Windows Hello for Business](/windows/security/identity-protection/hello-for-business/hello-hybrid-aadj-sso-base).
4749
>
Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
---
2+
title: Tenant management with Azure REST API
3+
description: Learn how to manage your Azure AD for customers tenant by calling the Azure REST API.
4+
services: active-directory
5+
author: garrodonnell
6+
manager: celested
7+
ms.author: godonnell
8+
ms.service: active-directory
9+
ms.workload: identity
10+
ms.subservice: ciam
11+
ms.topic: how-to
12+
ms.date: 05/23/2023
13+
ms.custom: developer
14+
15+
#Customer intent: As a dev, devops, I want to learn how to use the Azure REST API to manage my Azure AD for customers tenant.
16+
---
17+
18+
# Manage Azure Active Directory for customers tenant with Azure REST API
19+
You can manage your Azure Active Directory for your tenant using the Azure REST API. The management of resources related to tenant management supports the following API operations. Each link in the following sections targets the corresponding page within the Microsoft Graph API reference for that operation.
20+
21+
## Tenant Management operations
22+
23+
You can perform tenant management operations with your Azure Active Directory for customers tenant with the following operations:
24+
25+
- [Create or Update](/rest/api/azurestack/directory-tenants/create-or-update)
26+
- [Delete](/rest/api/azurestack/directory-tenants/delete)
27+
- [Get](/rest/api/azurestack/directory-tenants/get)
28+
- [List](/rest/api/azurestack/directory-tenants/list)
29+
30+
## Next steps
31+
32+
- To learn more about programmatic management, see [Microsoft Graph overview](/graph/overview).
Lines changed: 72 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,72 @@
1+
---
2+
title: Frequently asked questions
3+
description: Find answers to some of the most frequently asked questions about Microsoft Entra External ID for customers, also known as Azure Active Directory (Azure AD) for customers.
4+
services: active-directory
5+
author: msmimart
6+
manager: celestedg
7+
ms.service: active-directory
8+
ms.workload: identity
9+
ms.subservice: ciam
10+
ms.topic: reference
11+
ms.date: 05/23/2023
12+
ms.author: mimart
13+
ms.custom: it-pro
14+
---
15+
16+
# Microsoft Entra External ID for customers frequently asked questions
17+
18+
This article answers frequently asked questions about Microsoft Entra External ID for customers, also known as Azure Active Directory (Azure AD) for customers. This document offers guidance to help customers better understand Microsoft’s current external identities capabilities and the journey for our next generation platform (Microsoft Entra External ID).
19+
20+
This FAQ references customer identity and access management (CIAM). CIAM is an industry recognized category that covers solutions that manage identity, authentication, and authorization for external identity use cases (partners, customers, and citizens). Common functionality includes self-service capabilities, adaptive access, single sign-on (SSO), and bring your own identity (BYOI).
21+
22+
## Frequently asked questions
23+
24+
### What is Microsoft Entra External ID?
25+
26+
Microsoft Entra External ID is our next generation CIAM platform that represents an evolutionary step in unifying secure and engaging experiences across all external identities including customers, partners, citizens, and others, within a single, integrated platform.
27+
28+
### Is Microsoft Entra External ID a new name for Azure AD B2C?
29+
30+
No, this isn't a new name for Azure AD B2C. Microsoft Entra External ID builds on the success of our existing Azure AD B2C technologies but represents our future for CIAM. The new platform serves as the foundation for rapid innovation, features, and capabilities that address use cases across all external users.
31+
32+
### What is the release date for Microsoft Entra External ID?
33+
34+
Microsoft Entra External ID (for customers) entered preview at Microsoft Build 2023. The existing B2B collaboration feature remains unchanged.
35+
36+
### What is the pricing for Microsoft Entra External ID?
37+
38+
Microsoft Entra External ID (for customers) is in preview, so no pricing details are available at this time. The pricing for existing B2B collaboration features is unchanged.
39+
40+
### How does Microsoft Entra External ID affect B2B collaboration?
41+
42+
There are no changes to the existing B2B collaboration features or related pricing. Upon general availability, Microsoft Entra External ID will address use cases across all external user identities, including partners, customers, citizens, and others.
43+
44+
### How long will you support the current Azure AD B2C platform?
45+
46+
We remain fully committed to support of the current Azure AD B2C product. The SLA remains unchanged, and we’ll continue investments in the product to ensure security, availability, and reliability. For existing Azure AD B2C customers that have an interest in moving to the next generation platform, more details will be made available after general availability.
47+
48+
### I have many investments tied up in Azure AD B2C, both in code artifacts and CI/CD pipelines. Do I need to plan for a migration or some other effort?
49+
50+
We recognize the large investments in building and managing custom policies. We’ve listened to many customers who, like you, have shared that custom policies are too hard to build and manage. Our next generation platform will resolve the need for intricate custom policies. In addition to many other platform and feature improvements, you’ll have equivalent functionality in the new platform but a much easier way to build and manage it. We expect to share migration options closer to general availability of the next generation platform.
51+
52+
### I’ve heard I can preview the Microsoft Entra External ID platform. Where can I learn more?
53+
54+
You can learn more about the preview and the features we're delivering on the new platform by visiting the Microsoft Entra External ID for customers [developer center](https://aka.ms/ciam/dev).
55+
56+
### As a new customer, which solution is a better fit, Azure AD B2C or Microsoft Entra External ID (preview)?
57+
58+
Opt for the current Azure AD B2C product if:
59+
60+
- You have an immediate need to deploy a production ready build for customer-facing apps.
61+
62+
> [!NOTE]
63+
> Keep in mind that the next generation Microsoft Entra External ID platform represents the future of CIAM for Microsoft, and rapid innovation, new features and capabilities will be focused on this platform. By choosing the next generation platform from the start, you will receive the benefits of rapid innovation and a future-proof architecture.
64+
65+
Opt for the next generation Microsoft Entra External ID platform if:
66+
67+
- You’re starting fresh building identities into apps or you're in the early stages of product discovery.
68+
- The benefits of rapid innovation, new features and capabilities are a priority.
69+
70+
## Next steps
71+
72+
[Learn more about Microsoft Entra External ID for customers](index.yml)

0 commit comments

Comments
 (0)