Skip to content

Commit b1d223f

Browse files
committed
Merging changes synced from https://github.com/MicrosoftDocs/azure-docs-pr (branch live)
2 parents a97c40c + f40af7b commit b1d223f

File tree

203 files changed

+2141
-3187
lines changed

Some content is hidden

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

203 files changed

+2141
-3187
lines changed

.openpublishing.publish.config.json

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -632,6 +632,12 @@
632632
"branch": "master",
633633
"branch_mapping": {}
634634
},
635+
{
636+
"path_to_root": "samples-cosmosdb-mongodb-javascript",
637+
"url": "https://github.com/Azure-Samples/cosmos-db-mongodb-api-javascript-samples",
638+
"branch": "main",
639+
"branch_mapping": {}
640+
},
635641
{
636642
"path_to_root": "samples-cosmosdb-java-v4-web-app",
637643
"url": "https://github.com/Azure-Samples/azure-cosmos-java-sql-api-todo-app",

.openpublishing.redirection.json

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2399,6 +2399,21 @@
23992399
"redirect_url": "/azure/aks/ingress-tls",
24002400
"redirect_document_id": true
24012401
},
2402+
{
2403+
"source_path_from_root": "/articles/aks/ingress-internal-ip.md",
2404+
"redirect_url": "/azure/aks/ingress-basic",
2405+
"redirect_document_id": false
2406+
},
2407+
{
2408+
"source_path_from_root": "/articles/aks/ingress-own-tls.md",
2409+
"redirect_url": "/azure/aks/ingress-tls",
2410+
"redirect_document_id": false
2411+
},
2412+
{
2413+
"source_path_from_root": "/articles/aks/ingress-static-ip.md",
2414+
"redirect_url": "/azure/aks/ingress-tls",
2415+
"redirect_document_id": false
2416+
},
24022417
{
24032418
"source_path_from_root": "/articles/container-service/kubernetes/container-service-kubernetes-jenkins.md",
24042419
"redirect_url": "/azure/aks/jenkins-continuous-deployment",
@@ -18991,6 +19006,16 @@
1899119006
"redirect_url": "/azure/logic-apps/logic-apps-exception-handling",
1899219007
"redirect_document_id": false
1899319008
},
19009+
{
19010+
"source_path_from_root": "/articles/machine-learning/tutorial-power-bi-automated-model.md",
19011+
"redirect_url": "/azure/machine-learning/tutorial-power-bi-custom-model",
19012+
"redirect_document_id": false
19013+
},
19014+
{
19015+
"source_path_from_root": "/articles/machine-learning/tutorial-power-bi-designer-model.md",
19016+
"redirect_url": "/azure/machine-learning/tutorial-power-bi-custom-model",
19017+
"redirect_document_id": false
19018+
},
1899419019
{
1899519020
"source_path_from_root": "/articles/cognitive-services/LinguisticAnalysisAPI/AnalyzeMethod.md",
1899619021
"redirect_url": "/azure/machine-learning/classic-module-reference/text-analytics",
Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
11
---
2-
title: Microsoft Authenticator app authentication method - Azure Active Directory
3-
description: Learn about using the Microsoft Authenticator app in Azure Active Directory to help improve and secure sign-in events
2+
title: Microsoft Entra Authenticator app authentication method - Azure Active Directory
3+
description: Learn about using the Microsoft Entra Authenticator app in Azure Active Directory to help secure your sign-ins
44

55
services: active-directory
66
ms.service: active-directory
77
ms.subservice: authentication
88
ms.topic: conceptual
9-
ms.date: 10/29/2021
9+
ms.date: 06/09/2022
1010

1111
ms.author: justinha
1212
author: justinha
@@ -16,26 +16,26 @@ ms.collection: M365-identity-device-management
1616

1717
# Customer intent: As an identity administrator, I want to understand how to use the Microsoft Authenticator app in Azure AD to improve and secure user sign-in events.
1818
---
19-
# Authentication methods in Azure Active Directory - Microsoft Authenticator app
19+
# Authentication methods in Azure Active Directory - Microsoft Entra Authenticator app
2020

21-
The Microsoft Authenticator app provides an additional level of security to your Azure AD work or school account or your Microsoft account and is available for [Android](https://go.microsoft.com/fwlink/?linkid=866594) and [iOS](https://go.microsoft.com/fwlink/?linkid=866594). With the Microsoft Authenticator app, users can authenticate in a passwordless way during sign-in, or as an additional verification option during self-service password reset (SSPR) or Azure AD Multi-Factor Authentication events.
21+
The Microsoft Entra Authenticator app provides an additional level of security to your Azure AD work or school account or your Microsoft account and is available for [Android](https://go.microsoft.com/fwlink/?linkid=866594) and [iOS](https://go.microsoft.com/fwlink/?linkid=866594). With the Microsoft Authenticator app, users can authenticate in a passwordless way during sign-in, or as an additional verification option during self-service password reset (SSPR) or multifactor authentication events.
2222

2323
Users may receive a notification through the mobile app for them to approve or deny, or use the Authenticator app to generate an OATH verification code that can be entered in a sign-in interface. If you enable both a notification and verification code, users who register the Authenticator app can use either method to verify their identity.
2424

25-
To use the Authenticator app at a sign-in prompt rather than a username and password combination, see [Enable passwordless sign-in with the Microsoft Authenticator app](howto-authentication-passwordless-phone.md).
25+
To use the Authenticator app at a sign-in prompt rather than a username and password combination, see [Enable passwordless sign-in with the Microsoft Entra Authenticator app](howto-authentication-passwordless-phone.md).
2626

2727
> [!NOTE]
2828
> Users don't have the option to register their mobile app when they enable SSPR. Instead, users can register their mobile app at [https://aka.ms/mfasetup](https://aka.ms/mfasetup) or as part of the combined security info registration at [https://aka.ms/setupsecurityinfo](https://aka.ms/setupsecurityinfo).
2929
3030
## Passwordless sign-in
3131

32-
Instead of seeing a prompt for a password after entering a username, a user that has enabled phone sign-in from the Microsoft Authenticator app sees a message to enter a number in their app. When the correct number is selected, the sign-in process is complete.
32+
Instead of seeing a prompt for a password after entering a username, a user that has enabled phone sign-in from the Authenticator app sees a message to enter a number in their app. When the correct number is selected, the sign-in process is complete.
3333

3434
![Example of a browser sign-in asking for user to approve the sign-in.](./media/howto-authentication-passwordless-phone/phone-sign-in-microsoft-authenticator-app.png)
3535

3636
This authentication method provides a high level of security, and removes the need for the user to provide a password at sign-in.
3737

38-
To get started with passwordless sign-in, see [Enable passwordless sign-in with the Microsoft Authenticator app](howto-authentication-passwordless-phone.md).
38+
To get started with passwordless sign-in, see [Enable passwordless sign-in with the Microsoft Entra Authenticator app](howto-authentication-passwordless-phone.md).
3939

4040
## Notification through mobile app
4141

@@ -50,7 +50,7 @@ The Authenticator app can help prevent unauthorized access to accounts and stop
5050

5151
The Authenticator app can be used as a software token to generate an OATH verification code. After entering your username and password, you enter the code provided by the Authenticator app into the sign-in interface. The verification code provides a second form of authentication.
5252

53-
Users may have a combination of up to five OATH hardware tokens or authenticator applications, such as the Microsoft Authenticator app, configured for use at any time.
53+
Users may have a combination of up to five OATH hardware tokens or authenticator applications, such as the Authenticator app, configured for use at any time.
5454

5555
> [!WARNING]
5656
> To ensure the highest level of security for self-service password reset when only one method is required for reset, a verification code is the only option available to users.
@@ -59,6 +59,6 @@ Users may have a combination of up to five OATH hardware tokens or authenticator
5959
6060
## Next steps
6161

62-
To get started with passwordless sign-in, see [Enable passwordless sign-in with the Microsoft Authenticator app](howto-authentication-passwordless-phone.md).
62+
- To get started with passwordless sign-in, see [Enable passwordless sign-in with the Microsoft Entra Authenticator app](howto-authentication-passwordless-phone.md).
6363

64-
Learn more about configuring authentication methods using the [Microsoft Graph REST API](/graph/api/resources/authenticationmethods-overview).
64+
- Learn more about configuring authentication methods using the [Microsoft Graph REST API](/graph/api/resources/authenticationmethods-overview).

articles/active-directory/authentication/concept-authentication-passwordless.md

Lines changed: 16 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
11
---
22
title: Azure Active Directory passwordless sign-in
3-
description: Learn about options for passwordless sign-in to Azure Active Directory using FIDO2 security keys or the Microsoft Authenticator app
3+
description: Learn about options for passwordless sign-in to Azure Active Directory using FIDO2 security keys or the Microsoft Entra Authenticator app
44

55
services: active-directory
66
ms.service: active-directory
77
ms.subservice: authentication
88
ms.topic: conceptual
9-
ms.date: 06/28/2021
9+
ms.date: 06/09/2022
1010

1111
ms.author: justinha
1212
author: justinha
@@ -17,7 +17,7 @@ ms.collection: M365-identity-device-management
1717
---
1818
# Passwordless authentication options for Azure Active Directory
1919

20-
Features like multi-factor authentication (MFA) are a great way to secure your organization, but users often get frustrated with the additional security layer on top of having to remember their passwords. Passwordless authentication methods are more convenient because the password is removed and replaced with something you have, plus something you are or something you know.
20+
Features like multifactor authentication (MFA) are a great way to secure your organization, but users often get frustrated with the additional security layer on top of having to remember their passwords. Passwordless authentication methods are more convenient because the password is removed and replaced with something you have, plus something you are or something you know.
2121

2222
| Authentication | Something you have | Something you are or know |
2323
| --- | --- | --- |
@@ -26,7 +26,7 @@ Features like multi-factor authentication (MFA) are a great way to secure your o
2626
Each organization has different needs when it comes to authentication. Microsoft global Azure and Azure Government offer the following three passwordless authentication options that integrate with Azure Active Directory (Azure AD):
2727

2828
- Windows Hello for Business
29-
- Microsoft Authenticator app
29+
- Microsoft Entra Authenticator app
3030
- FIDO2 security keys
3131

3232
![Authentication: Security versus convenience](./media/concept-authentication-passwordless/passwordless-convenience-security.png)
@@ -45,21 +45,21 @@ The following steps show how the sign-in process works with Azure AD:
4545
1. The Cloud AP provider requests a nonce (a random arbitrary number that can be used just once) from Azure AD.
4646
1. Azure AD returns a nonce that's valid for 5 minutes.
4747
1. The Cloud AP provider signs the nonce using the user's private key and returns the signed nonce to the Azure AD.
48-
1. Azure AD validates the signed nonce using the user's securely registered public key against the nonce signature. After validating the signature, Azure AD then validates the returned signed nonce. When the nonce is validated, Azure AD creates a primary refresh token (PRT) with session key that is encrypted to the device's transport key and returns it to the Cloud AP provider.
49-
1. The Cloud AP provider receives the encrypted PRT with session key. Using the device's private transport key, the Cloud AP provider decrypts the session key and protects the session key using the device's Trusted Platform Module (TPM).
48+
1. Azure AD validates the signed nonce using the user's securely registered public key against the nonce signature. Azure AD validates the signature and then validates the returned signed nonce. When the nonce is validated, Azure AD creates a primary refresh token (PRT) with session key that is encrypted to the device's transport key and returns it to the Cloud AP provider.
49+
1. The Cloud AP provider receives the encrypted PRT with session key. The Cloud AP provider uses the device's private transport key to decrypt the session key and protects the session key using the device's Trusted Platform Module (TPM).
5050
1. The Cloud AP provider returns a successful authentication response to Windows. The user is then able to access Windows as well as cloud and on-premises applications without the need to authenticate again (SSO).
5151

5252
The Windows Hello for Business [planning guide](/windows/security/identity-protection/hello-for-business/hello-planning-guide) can be used to help you make decisions on the type of Windows Hello for Business deployment and the options you'll need to consider.
5353

54-
## Microsoft Authenticator App
54+
## Microsoft Entra Authenticator App
5555

56-
You can also allow your employee's phone to become a passwordless authentication method. You may already be using the Microsoft Authenticator App as a convenient multi-factor authentication option in addition to a password. You can also use the Authenticator App as a passwordless option.
56+
You can also allow your employee's phone to become a passwordless authentication method. You may already be using the Authenticator app as a convenient multi-factor authentication option in addition to a password. You can also use the Authenticator App as a passwordless option.
5757

58-
![Sign in to Microsoft Edge with the Microsoft Authenticator app](./media/concept-authentication-passwordless/concept-web-sign-in-microsoft-authenticator-app.png)
58+
![Sign in to Microsoft Edge with the Microsoft Entra Authenticator app](./media/concept-authentication-passwordless/concept-web-sign-in-microsoft-authenticator-app.png)
5959

60-
The Authenticator App turns any iOS or Android phone into a strong, passwordless credential. Users can sign in to any platform or browser by getting a notification to their phone, matching a number displayed on the screen to the one on their phone, and then using their biometric (touch or face) or PIN to confirm. Refer to [Download and install the Microsoft Authenticator app](https://support.microsoft.com/account-billing/download-and-install-the-microsoft-authenticator-app-351498fc-850a-45da-b7b6-27e523b8702a) for installation details.
60+
The Authenticator App turns any iOS or Android phone into a strong, passwordless credential. Users can sign in to any platform or browser by getting a notification to their phone, matching a number displayed on the screen to the one on their phone, and then using their biometric (touch or face) or PIN to confirm. Refer to [Download and install the Microsoft Entra Authenticator app](https://support.microsoft.com/account-billing/download-and-install-the-microsoft-authenticator-app-351498fc-850a-45da-b7b6-27e523b8702a) for installation details.
6161

62-
Passwordless authentication using the Authenticator app follows the same basic pattern as Windows Hello for Business. It's a little more complicated as the user needs to be identified so that Azure AD can find the Microsoft Authenticator App version being used:
62+
Passwordless authentication using the Authenticator app follows the same basic pattern as Windows Hello for Business. It's a little more complicated as the user needs to be identified so that Azure AD can find the Authenticator app version being used:
6363

6464
![Diagram that outlines the steps involved for user sign-in with the Microsoft Authenticator App](./media/concept-authentication-passwordless/authenticator-app-flow.png)
6565

@@ -163,7 +163,7 @@ The following considerations apply:
163163
- Users can register and manage these passwordless authentication methods in their account portal.
164164

165165
- Users can sign in with these passwordless authentication methods:
166-
- Microsoft Authenticator App: Works in scenarios where Azure AD authentication is used, including across all browsers, during Windows 10 setup, and with integrated mobile apps on any operating system.
166+
- Authenticator app: Works in scenarios where Azure AD authentication is used, including across all browsers, during Windows 10 setup, and with integrated mobile apps on any operating system.
167167
- Security keys: Work on lock screen for Windows 10 and the web in supported browsers like Microsoft Edge (both legacy and new Edge).
168168

169169
- Users can use passwordless credentials to access resources in tenants where they are a guest, but they may still be required to perform MFA in that resource tenant. For more information, see [Possible double multi-factor authentication](../external-identities/current-limitations.md#possible-double-multi-factor-authentication).
@@ -177,9 +177,9 @@ The choice between these three passwordless options depends on your company's se
177177

178178
Here are some factors for you to consider when choosing Microsoft passwordless technology:
179179

180-
||**Windows Hello for Business**|**Passwordless sign-in with the Microsoft Authenticator app**|**FIDO2 security keys**|
180+
||**Windows Hello for Business**|**Passwordless sign-in with the Authenticator app**|**FIDO2 security keys**|
181181
|:-|:-|:-|:-|
182-
|**Pre-requisite**| Windows 10, version 1809 or later<br>Azure Active Directory| Microsoft Authenticator app<br>Phone (iOS and Android devices running Android 6.0 or above.)|Windows 10, version 1903 or later<br>Azure Active Directory|
182+
|**Pre-requisite**| Windows 10, version 1809 or later<br>Azure Active Directory| Authenticator app<br>Phone (iOS and Android devices running Android 6.0 or above.)|Windows 10, version 1903 or later<br>Azure Active Directory|
183183
|**Mode**|Platform|Software|Hardware|
184184
|**Systems and devices**|PC with a built-in Trusted Platform Module (TPM)<br>PIN and biometrics recognition |PIN and biometrics recognition on phone|FIDO2 security devices that are Microsoft compatible|
185185
|**User experience**|Sign in using a PIN or biometric recognition (facial, iris, or fingerprint) with Windows devices.<br>Windows Hello authentication is tied to the device; the user needs both the device and a sign-in component such as a PIN or biometric factor to access corporate resources.|Sign in using a mobile phone with fingerprint scan, facial or iris recognition, or PIN.<br>Users sign in to work or personal account from their PC or mobile phone.|Sign in using FIDO2 security device (biometrics, PIN, and NFC)<br>User can access device based on organization controls and authenticate based on PIN, biometrics using devices such as USB security keys and NFC-enabled smartcards, keys, or wearables.|
@@ -190,9 +190,9 @@ Use the following table to choose which method will support your requirements an
190190
|Persona|Scenario|Environment|Passwordless technology|
191191
|:-|:-|:-|:-|
192192
|**Admin**|Secure access to a device for management tasks|Assigned Windows 10 device|Windows Hello for Business and/or FIDO2 security key|
193-
|**Admin**|Management tasks on non-Windows devices| Mobile or non-windows device|Passwordless sign-in with the Microsoft Authenticator app|
193+
|**Admin**|Management tasks on non-Windows devices| Mobile or non-windows device|Passwordless sign-in with the Authenticator app|
194194
|**Information worker**|Productivity work|Assigned Windows 10 device|Windows Hello for Business and/or FIDO2 security key|
195-
|**Information worker**|Productivity work| Mobile or non-windows device|Passwordless sign-in with the Microsoft Authenticator app|
195+
|**Information worker**|Productivity work| Mobile or non-windows device|Passwordless sign-in with the Authenticator app|
196196
|**Frontline worker**|Kiosks in a factory, plant, retail, or data entry|Shared Windows 10 devices|FIDO2 Security keys|
197197

198198
## Next steps

0 commit comments

Comments
 (0)