Skip to content

Commit 1e2bcc0

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into 2023397-c
2 parents 9b26ed1 + 500b9ee commit 1e2bcc0

File tree

586 files changed

+13712
-5674
lines changed

Some content is hidden

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

586 files changed

+13712
-5674
lines changed

.openpublishing.redirection.active-directory.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4416,6 +4416,11 @@
44164416
"redirect_url": "/azure/active-directory/reports-monitoring/howto-configure-prerequisites-for-reporting-api",
44174417
"redirect_document_id": false
44184418
},
4419+
{
4420+
"source_path_from_root": "/articles/active-directory/reports-monitoring/reference-reports-latencies.md",
4421+
"redirect_url": "/azure/active-directory/reports-monitoring/reference-azure-ad-sla-performance",
4422+
"redirect_document_id": false
4423+
},
44194424
{
44204425
"source_path_from_root": "/articles/active-directory/customize-branding.md",
44214426
"redirect_url": "/azure/active-directory/fundamentals/customize-branding",

.openpublishing.redirection.azure-monitor.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5701,6 +5701,11 @@
57015701
"source_path_from_root": "/articles/azure-monitor/autoscale/autoscale-resource-log-schema.md",
57025702
"redirect_url": "/azure/azure-monitor/autoscale/autoscale-diagnostics",
57035703
"redirect_document_id": false
5704+
},
5705+
{
5706+
"source_path_from_root": "/articles/azure-monitor/alerts/proactive-performance-diagnostics.md",
5707+
"redirect_url": "https://azure.microsoft.com/updates/public-preview-alerts-based-smart-detection-for-application-insights/",
5708+
"redirect_document_id": false
57045709
}
57055710
]
57065711
}

.openpublishing.redirection.json

Lines changed: 5 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -13444,16 +13444,6 @@
1344413444
"redirect_url": "/azure/logic-apps/logic-apps-exception-handling",
1344513445
"redirect_document_id": false
1344613446
},
13447-
{
13448-
"source_path_from_root": "/articles/machine-learning/tutorial-power-bi-automated-model.md",
13449-
"redirect_url": "/azure/machine-learning/tutorial-power-bi-custom-model",
13450-
"redirect_document_id": false
13451-
},
13452-
{
13453-
"source_path_from_root": "/articles/machine-learning/tutorial-power-bi-designer-model.md",
13454-
"redirect_url": "/azure/machine-learning/tutorial-power-bi-custom-model",
13455-
"redirect_document_id": false
13456-
},
1345713447
{
1345813448
"source_path_from_root": "/articles/event-grid/cli-samples.md",
1345913449
"redirect_url": "/azure/event-grid/scripts/event-grid-cli-subscribe-custom-topic",
@@ -22671,6 +22661,11 @@
2267122661
"redirect_URL": "/azure/route-server/tutorial-protect-route-server-ddos",
2267222662
"redirect_document_id": false
2267322663
},
22664+
{
22665+
"source_path": "articles/external-attack-surface-management/data-connections-overview.md",
22666+
"redirect_URL": "/azure/external-attack-surface-management/index",
22667+
"redirect_document_id": true
22668+
},
2267422669
{
2267522670
"source_path": "articles/virtual-network/nat-gateway/tutorial-protect-nat-gateway.md",
2267622671
"redirect_URL": "/azure/virtual-network/nat-gateway/tutorial-protect-nat-gateway-ddos",

articles/active-directory/authentication/certificate-based-authentication-faq.yml

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -120,9 +120,15 @@ sections:
120120
The browser caches the certificate after the certificate picker appears. If the user retries, the cached certificate is used automatically. The user should close the browser, and reopen a new session to try CBA again.
121121
122122
- question: |
123-
Why can't single-factor certificates be used to complete MFA?
123+
Why does not proof up for registering other auth methods come up when I use single factor certificates?
124124
answer: |
125-
There's no support for a second factor when the first factor is a single-factor certificate. We're working to add support for second factors.
125+
A user will be considered MFA capable when a user is in scope for Certificate-based authentication auth method. This means user will not be able to use proof up as part of their authentication to registerd other available methods and should have MFA via another method to register other available auth methods.
126+
127+
- question: |
128+
How can I use single-factor certificates to complete MFA?
129+
answer: |
130+
We have support for single factor CBA to get MFA. CBA SF + PSI (passwordless phone sign in) and CBA SF + FIDO2 are the two supported combinations to get MFA using single factor certificates.
131+
[MFA with single factor certificates](../authentication/concept-certificate-based-authentication-technical-deep-dive.md#mfa-authentication-flow-using-single-factor-certificates-and-passwordless-sign-in)
126132
127133
- question: |
128134
Will the changes to the Authentication methods policy take effect immediately?

articles/active-directory/authentication/concept-authentication-phone-options.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ To work properly, phone numbers must be in the format *+CountryCode PhoneNumber*
3030
> [!NOTE]
3131
> There needs to be a space between the country/region code and the phone number.
3232
>
33-
> Password reset doesn't support phone extensions. Even in the *+1 4251234567X12345* format, extensions are removed before the call is placed.
33+
> Password reset and Azure AD Multi-Factor Authentication don't support phone extensions. Even in the *+1 4251234567X12345* format, extensions are removed before the call is placed.
3434
3535
## Mobile phone verification
3636

articles/active-directory/authentication/concept-certificate-based-authentication-migration.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -39,6 +39,9 @@ To configure Staged Rollout, follow these steps:
3939

4040
For more information, see [Staged Rollout](../hybrid/how-to-connect-staged-rollout.md).
4141

42+
>[!NOTE]
43+
> When Staged rollout is enabled for a user, the user is considered a managed user and all authentication will happen at Azure AD. For a federated Tenant, if CBA is enabled on Staged Rollout, password authentication only works if PHS is enabled too otherwise password authentication will fail.
44+
4245
## Use Azure AD connect to update certificateUserIds attribute
4346

4447
An AD FS admin can use **Synchronization Rules Editor** to create rules to sync the values of attributes from AD FS to Azure AD user objects. For more information, see [Sync rules for certificateUserIds](concept-certificate-based-authentication-certificateuserids.md#update-certificate-user-ids-using-azure-ad-connect).

articles/active-directory/authentication/concept-certificate-based-authentication-technical-deep-dive.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -72,9 +72,12 @@ Now we'll walk through each step:
7272
1. Azure AD completes the sign-in process by sending a primary refresh token back to indicate successful sign-in.
7373
1. If the user sign-in is successful, the user can access the application.
7474

75-
## Single-factor certificate-based authentication
75+
## MFA with Single-factor certificate-based authentication
7676

77-
Azure AD CBA supports second factors to meet MFA requirements with single-factor certificates. Users can use either passwordless sign-in or FIDO2 security keys as second factors when the first factor is single-factor CBA. Users need to register passwordless sign-in or FIDO2 in advance to signing in with Azure AD CBA.
77+
Azure AD CBA supports second factors to meet MFA requirements with single-factor certificates. Users can use either passwordless sign-in or FIDO2 security keys as second factors when the first factor is single-factor CBA. Users need to have another way to get MFA and register passwordless sign-in or FIDO2 in advance to signing in with Azure AD CBA.
78+
79+
>[!IMPORTANT]
80+
>A user will be considered MFA capable when a user is in scope for Certificate-based authentication auth method. This means user will not be able to use proof up as part of their authentication to registerd other available methods. More info on [Azure AD MFA](../authentication/concept-mfa-howitworks.md)
7881
7982
**Steps to set up passwordless phone signin(PSI) with CBA**
8083

articles/active-directory/cloud-infrastructure-entitlement-management/how-to-add-remove-user-to-group.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ This article describes how you can add or remove a new user for a group in Permi
2121
2222
## Add a user
2323

24-
1. Navigate to the [Microsoft Entra admin center](https://entr.microsoft.com/#home).
24+
1. Navigate to the [Microsoft Entra admin center](https://entra.microsoft.com/#home).
2525
1. From the Azure Active Directory tile, select **Go to Azure Active Directory**.
2626
1. From the navigation pane, select the **Groups** drop-down menu, then **All groups**.
2727
1. Select the group name for the group you want to add the user to.
@@ -37,7 +37,7 @@ This article describes how you can add or remove a new user for a group in Permi
3737

3838
## Remove a user
3939

40-
1. Navigate to the Microsoft [Entra admin center](https://entr.microsoft.com/#home).
40+
1. Navigate to the Microsoft [Entra admin center](https://entra.microsoft.com/#home).
4141
1. From the Azure Active Directory tile, select **Go to Azure Active Directory**.
4242
1. From the navigation pane, select the **Groups** drop-down menu, then **All groups**.
4343
1. Select the group name for the group you want to remove the user from.

articles/active-directory/cloud-sync/how-to-prerequisites.md

Lines changed: 5 additions & 42 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ You need the following to use Azure AD Connect cloud sync:
2626
- On-premises firewall configurations.
2727

2828
## Group Managed Service Accounts
29-
A group Managed Service Account is a managed domain account that provides automatic password management, simplified service principal name (SPN) management,the ability to delegate the management to other administrators, and also extends this functionality over multiple servers. Azure AD Connect Cloud Sync supports and uses a gMSA for running the agent. You will be prompted for administrative credentials during setup, in order to create this account. The account will appear as (domain\provAgentgMSA$). For more information on a gMSA, see [Group Managed Service Accounts](/windows-server/security/group-managed-service-accounts/group-managed-service-accounts-overview)
29+
A group Managed Service Account is a managed domain account that provides automatic password management, simplified service principal name (SPN) management, the ability to delegate the management to other administrators, and also extends this functionality over multiple servers. Azure AD Connect Cloud Sync supports and uses a gMSA for running the agent. You will be prompted for administrative credentials during setup, in order to create this account. The account will appear as (domain\provAgentgMSA$). For more information on a gMSA, see [group Managed Service Accounts](/windows-server/security/group-managed-service-accounts/group-managed-service-accounts-overview)
3030

3131
### Prerequisites for gMSA:
3232
1. The Active Directory schema in the gMSA domain's forest needs to be updated to Windows Server 2012 or later.
@@ -48,46 +48,9 @@ If you are creating a custom gMSA account, you need to ensure that the account h
4848
|Allow |gMSA Account |Read all properties |Descendant Contact objects|
4949
|Allow |gMSA Account |Create/delete User objects|This object and all descendant objects|
5050

51-
For steps on how to upgrade an existing agent to use a gMSA account see [Group Managed Service Accounts](how-to-install.md#group-managed-service-accounts).
52-
53-
#### Create gMSA account with PowerShell
54-
You can use the following PowerShell script to create a custom gMSA account. Then you can use the [cloud sync gMSA cmdlets](how-to-gmsa-cmdlets.md) to apply more granular permissions.
55-
56-
```powershell
57-
# Filename: 1_SetupgMSA.ps1
58-
# Description: Creates and installs a custom gMSA account for use with Azure AD Connect cloud sync.
59-
#
60-
# DISCLAIMER:
61-
# Copyright (c) Microsoft Corporation. All rights reserved. This
62-
# script is made available to you without any express, implied or
63-
# statutory warranty, not even the implied warranty of
64-
# merchantability or fitness for a particular purpose, or the
65-
# warranty of title or non-infringement. The entire risk of the
66-
# use or the results from the use of this script remains with you.
67-
#
68-
#
69-
#
70-
#
71-
# Declare variables
72-
$Name = 'provAPP1gMSA'
73-
$Description = "Azure AD Cloud Sync service account for APP1 server"
74-
$Server = "APP1.contoso.com"
75-
$Principal = Get-ADGroup 'Domain Computers'
76-
77-
# Create service account in Active Directory
78-
New-ADServiceAccount -Name $Name `
79-
-Description $Description `
80-
-DNSHostName $Server `
81-
-ManagedPasswordIntervalInDays 30 `
82-
-PrincipalsAllowedToRetrieveManagedPassword $Principal `
83-
-Enabled $True `
84-
-PassThru
85-
86-
# Install the new service account on Azure AD Cloud Sync server
87-
Install-ADServiceAccount -Identity $Name
88-
```
89-
90-
For additional information on the cmdlets above, see [Getting Started with Group Managed Service Accounts](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/jj128431(v=ws.11)?redirectedfrom=MSDN).
51+
For steps on how to upgrade an existing agent to use a gMSA account see [group Managed Service Accounts](how-to-install.md#group-managed-service-accounts).
52+
53+
For more information on how to prepare your Active Directory for group Managed Service Account, see [group Managed Service Accounts Overview](/windows-server/security/group-managed-service-accounts/group-managed-service-accounts-overview).
9154

9255
### In the Azure Active Directory admin center
9356

@@ -104,7 +67,7 @@ Run the [IdFix tool](/office365/enterprise/prepare-directory-attributes-for-sync
10467

10568
2. The PowerShell execution policy on the local server must be set to Undefined or RemoteSigned.
10669

107-
3. If there's a firewall between your servers and Azure AD, configure see [Firewall and proxy requirements](#firewall-and-proxy-requirements) below.
70+
3. If there's a firewall between your servers and Azure AD, see [Firewall and proxy requirements](#firewall-and-proxy-requirements) below.
10871

10972
>[!NOTE]
11073
> Installing the cloud provisioning agent on Windows Server Core is not supported.

articles/active-directory/develop/console-quickstart-portal-nodejs.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -25,8 +25,7 @@ ms.custom: mode-api
2525
2626
> [!div renderon="portal" id="display-on-portal" class="sxs-lookup"]
2727
> # Quickstart: Acquire a token and call Microsoft Graph API from a Node.js console app using app's identity
28-
>
29-
> [!div renderon="portal" class="sxs-lookup"]
28+
>
3029
> In this quickstart, you download and run a code sample that demonstrates how a Node.js console application can get an access token using the app's identity to call the Microsoft Graph API and display a [list of users](/graph/api/user-list) in the directory. The code sample demonstrates how an unattended job or Windows service can run with an application identity, instead of a user's identity.
3130
>
3231
> This quickstart uses the [Microsoft Authentication Library for Node.js (MSAL Node)](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/lib/msal-node) with the [client credentials grant](v2-oauth2-client-creds-grant-flow.md).

0 commit comments

Comments
 (0)