Skip to content

Commit 81f649a

Browse files
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into t581147p
2 parents f7570cf + 7f6e9cd commit 81f649a

File tree

1,033 files changed

+15262
-9130
lines changed

Some content is hidden

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

1,033 files changed

+15262
-9130
lines changed

.openpublishing.redirection.json

Lines changed: 55 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -638,6 +638,21 @@
638638
"redirect_url": "/azure/azure-arc/kubernetes/conceptual-agent-overview",
639639
"redirect_document_id": false
640640
},
641+
{
642+
"source_path": "articles/cognitive-services/conversational-language-understanding/how-to/deploy-query-model.md",
643+
"redirect_url": "/azure/cognitive-services/language-service/conversational-language-understanding/how-to/deploy-model",
644+
"redirect_document_id": true
645+
},
646+
{
647+
"source_path": "articles/cognitive-services/conversational-language-understanding/fail-over.md",
648+
"redirect_url": "/azure/cognitive-services/language-service/conversational-language-understanding/how-to/fail-over",
649+
"redirect_document_id": true
650+
},
651+
{
652+
"source_path": "articles/cognitive-services/orchestration-workflow/deploy-query-model.md",
653+
"redirect_url": "/azure/cognitive-services/language-service/orchestration-workflow/how-to/call-api",
654+
"redirect_document_id": true
655+
},
641656
{
642657
"source_path": "articles/cognitive-services/whats-new-docs.md",
643658
"redirect_url": "/azure/cognitive-services/what-are-cognitive-services",
@@ -17818,6 +17833,26 @@
1781817833
"redirect_url": "/azure/iot-dps/quick-setup-auto-provision-cli",
1781917834
"redirect_document_id": false
1782017835
},
17836+
{
17837+
"source_path_from_root": "/articles/iot-dps/tutorial-net-provision-device-to-hub.md",
17838+
"redirect_url": "/azure/iot-dps/",
17839+
"redirect_document_id": false
17840+
},
17841+
{
17842+
"source_path_from_root": "/articles/iot-dps/tutorial-provision-device-to-hub.md",
17843+
"redirect_url": "/azure/iot-dps/quick-create-simulated-device-symm-key",
17844+
"redirect_document_id": false
17845+
},
17846+
{
17847+
"source_path_from_root": "/articles/iot-dps/tutorial-set-up-cloud.md",
17848+
"redirect_url": "/azure/iot-dps/quick-create-simulated-device-symm-key",
17849+
"redirect_document_id": false
17850+
},
17851+
{
17852+
"source_path_from_root": "/articles/iot-dps/tutorial-set-up-device.md",
17853+
"redirect_url": "/azure/iot-dps/quick-create-simulated-device-symm-key",
17854+
"redirect_document_id": false
17855+
},
1782117856
{
1782217857
"source_path_from_root": "/articles/security/fundamentals/iot-overview.md",
1782317858
"redirect_url": "/azure/iot-fundamentals/iot-security-architecture",
@@ -21189,6 +21224,16 @@
2118921224
"redirect_url": "/azure/machine-learning/v1/reference-pipeline-yaml",
2119021225
"redirect_document_id": false
2119121226
},
21227+
{
21228+
"source_path_from_root": "/articles/machine-learning/how-to-create-register-datasets.md",
21229+
"redirect_url": "/azure/machine-learning/how-to-create-register-data-assets",
21230+
"redirect_document_id": false
21231+
},
21232+
{
21233+
"source_path_from_root": "/articles/machine-learning/how-to-access-data.md",
21234+
"redirect_url": "/azure/machine-learning/how-to-datastore",
21235+
"redirect_document_id": false
21236+
},
2119221237
{
2119321238
"source_path_from_root": "/articles/machine-learning/how-to-deploy-azure-container-instance.md",
2119421239
"redirect_url": "/azure/machine-learning/v1/how-to-deploy-azure-container-instance",
@@ -42759,6 +42804,11 @@
4275942804
"redirect_url": "/azure/aks/open-service-mesh-integrations",
4276042805
"redirect_document_id": false
4276142806
},
42807+
{
42808+
"source_path_from_root": "/articles/aks/spark-job.md",
42809+
"redirect_url": "/azure/aks/integrations#open-source-and-third-party-integrations",
42810+
"redirect_document_id": false
42811+
},
4276242812
{
4276342813
"source_path_from_root": "/articles/iot-dps/quick-create-device-symmetric-key-csharp.md",
4276442814
"redirect_url": "/azure/iot-dps/quick-create-simulated-device-symm-key",
@@ -43238,6 +43288,11 @@
4323843288
"source_path_from_root": "/articles/cognitive-services/language-service/text-summarization/quickstart.md",
4323943289
"redirect_url": "/azure/cognitive-services/language-service/summarization/quickstart",
4324043290
"redirect_document_id": true
43291+
},
43292+
{
43293+
"source_path_from_root": "/articles/aks/web-app-routing.md",
43294+
"redirect_url": "/azure/aks/intro-kubernetes",
43295+
"redirect_document_id": false
4324143296
}
4324243297
]
4324343298
}

articles/active-directory-b2c/partner-xid.md

Lines changed: 159 additions & 41 deletions
Large diffs are not rendered by default.

articles/active-directory-b2c/whats-new-docs.md

Lines changed: 25 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "What's new in Azure Active Directory business-to-customer (B2C)"
33
description: "New and updated documentation for the Azure Active Directory business-to-customer (B2C)."
4-
ms.date: 04/04/2022
4+
ms.date: 05/23/2022
55
ms.service: active-directory
66
ms.subservice: B2C
77
ms.topic: reference
@@ -15,6 +15,30 @@ manager: CelesteDG
1515

1616
Welcome to what's new in Azure Active Directory B2C documentation. This article lists new docs that have been added and those that have had significant updates in the last three months. To learn what's new with the B2C service, see [What's new in Azure Active Directory](../active-directory/fundamentals/whats-new.md).
1717

18+
## April 2022
19+
20+
### New articles
21+
22+
- [Tutorial: Configure Azure Web Application Firewall with Azure Active Directory B2C](partner-azure-web-application-firewall.md)
23+
- [Configure Asignio with Azure Active Directory B2C for multi-factor authentication](partner-asignio.md)
24+
- [Set up sign-up and sign-in with Mobile ID using Azure Active Directory B2C](identity-provider-mobile-id.md)
25+
- [Find help and open a support ticket for Azure Active Directory B2C](find-help-open-support-ticket.md)
26+
27+
### Updated articles
28+
29+
- [Configure authentication in a sample single-page application by using Azure AD B2C](configure-authentication-sample-spa-app.md)
30+
- [Configure xID with Azure Active Directory B2C for passwordless authentication](partner-xid.md)
31+
- [Azure Active Directory B2C service limits and restrictions](service-limits.md)
32+
- [Localization string IDs](localization-string-ids.md)
33+
- [Manage your Azure Active Directory B2C tenant](tenant-management.md)
34+
- [Page layout versions](page-layout.md)
35+
- [Secure your API used an API connector in Azure AD B2C](secure-rest-api.md)
36+
- [Azure Active Directory B2C: What's new](whats-new-docs.md)
37+
- [Application types that can be used in Active Directory B2C](application-types.md)
38+
- [Publish your Azure Active Directory B2C app to the Azure Active Directory app gallery](publish-app-to-azure-ad-app-gallery.md)
39+
- [Quickstart: Set up sign in for a desktop app using Azure Active Directory B2C](quickstart-native-app-desktop.md)
40+
- [Register a single-page application (SPA) in Azure Active Directory B2C](tutorial-register-spa.md)
41+
1842
## March 2022
1943

2044
### New articles

articles/active-directory/authentication/howto-authentication-passwordless-security-key-on-premises.md

Lines changed: 1 addition & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -288,17 +288,10 @@ Make sure that enough DCs are patched to respond in time to service your resourc
288288
> [!NOTE]
289289
> The `/keylist` switch in the `nltest` command is available in client Windows 10 v2004 and later.
290290
291-
### What if I have a CloudTGT but it never gets exchange for a OnPremTGT when I am using Windows Hello for Business Cloud Trust?
292-
293-
Make sure that the user you are signed in as, is a member of the groups of users that can use FIDO2 as an authentication method, or enable it for all users.
294-
295-
> [!NOTE]
296-
> Even if you are not explicitly using a security key to sign-in to your device, the underlying technology is dependent on the FIDO2 infrastructure requirements.
297-
298291
### Do FIDO2 security keys work in a Windows login with RODC present in the hybrid environment?
299292

300293
An FIDO2 Windows login looks for a writable DC to exchange the user TGT. As long as you have at least one writable DC per site, the login works fine.
301294

302295
## Next steps
303296

304-
[Learn more about passwordless authentication](concept-authentication-passwordless.md)
297+
[Learn more about passwordless authentication](concept-authentication-passwordless.md)

articles/active-directory/conditional-access/block-legacy-authentication.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -85,7 +85,7 @@ For more information about these authentication protocols and services, see [Sig
8585

8686
Before you can block legacy authentication in your directory, you need to first understand if your users have apps that use legacy authentication and how it affects your overall directory. Azure AD sign-in logs can be used to understand if you're using legacy authentication.
8787

88-
1. Navigate to the **Azure portal** > **Azure Active Directory** > **Sign-ins**.
88+
1. Navigate to the **Azure portal** > **Azure Active Directory** > **Sign-in logs**.
8989
1. Add the Client App column if it isn't shown by clicking on **Columns** > **Client App**.
9090
1. **Add filters** > **Client App** > select all of the legacy authentication protocols. Select outside the filtering dialog box to apply your selections and close the dialog box.
9191
1. If you've activated the [new sign-in activity reports preview](../reports-monitoring/concept-all-sign-ins.md), repeat the above steps also on the **User sign-ins (non-interactive)** tab.

articles/active-directory/conditional-access/howto-conditional-access-session-lifetime.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ The Azure Active Directory (Azure AD) default configuration for user sign-in fre
3636

3737
It might sound alarming to not ask for a user to sign back in, in reality any violation of IT policies will revoke the session. Some examples include (but aren't limited to) a password change, an incompliant device, or account disable. You can also explicitly [revoke users’ sessions using PowerShell](/powershell/module/azuread/revoke-azureaduserallrefreshtoken). The Azure AD default configuration comes down to “don’t ask users to provide their credentials if security posture of their sessions hasn't changed”.
3838

39-
The sign-in frequency setting works with apps that have implemented OAUTH2 or OIDC protocols according to the standards. Most Microsoft native apps for Windows, Mac, and Mobile including the following web applications comply with the setting.
39+
The sign-in frequency setting works with apps that have implemented OAuth2 or OIDC protocols according to the standards. Most Microsoft native apps for Windows, Mac, and Mobile including the following web applications comply with the setting.
4040

4141
- Word, Excel, PowerPoint Online
4242
- OneNote Online
@@ -48,7 +48,7 @@ The sign-in frequency setting works with apps that have implemented OAUTH2 or OI
4848
- Dynamics CRM Online
4949
- Azure portal
5050

51-
The sign-in frequency setting works with SAML applications as well, as long as they don't drop their own cookies and are redirected back to Azure AD for authentication on regular basis.
51+
The sign-in frequency setting works with 3rd party SAML applications and apps that have implemented OAuth2 or OIDC protocols, as long as they don't drop their own cookies and are redirected back to Azure AD for authentication on regular basis.
5252

5353
### User sign-in frequency and multi-factor authentication
5454

articles/active-directory/develop/active-directory-optional-claims.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -351,7 +351,7 @@ This section covers the configuration options under optional claims for changing
351351
{
352352
"name": "groups",
353353
"additionalProperties": [
354-
"netbios_name_and_sam_account_name",
354+
"netbios_domain_and_sam_account_name",
355355
"emit_as_roles"
356356
]
357357
}
@@ -360,7 +360,7 @@ This section covers the configuration options under optional claims for changing
360360
{
361361
"name": "groups",
362362
"additionalProperties": [
363-
"netbios_name_and_sam_account_name",
363+
"netbios_domain_and_sam_account_name",
364364
"emit_as_roles"
365365
]
366366
}

articles/active-directory/develop/active-directory-v2-protocols.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -77,6 +77,11 @@ https://login.microsoftonline.com/<issuer>/oauth2/v2.0/token
7777

7878
# NOTE: These are examples. Endpoint URI format may vary based on application type,
7979
# sign-in audience, and Azure cloud instance (global or national cloud).
80+
81+
# The {issuer} value in the path of the request can be used to control who can sign into the application.
82+
# The allowed values are **common** for both Microsoft accounts and work or school accounts,
83+
# **organizations** for work or school accounts only, **consumers** for Microsoft accounts only,
84+
# and **tenant identifiers** such as the tenant ID or domain name.
8085
```
8186

8287
To find the endpoints for an application you've registered, in the [Azure portal](https://portal.azure.com) navigate to:

articles/active-directory/develop/sample-v2-code.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -108,7 +108,7 @@ The following samples show an application that accesses the Microsoft Graph API
108108
> |.NET Core| &#8226; [Call Microsoft Graph](https://github.com/Azure-Samples/active-directory-dotnetcore-daemon-v2/tree/master/1-Call-MSGraph) <br/> &#8226; [Call web API](https://github.com/Azure-Samples/active-directory-dotnetcore-daemon-v2/tree/master/2-Call-OwnApi)<br/> &#8226; [Call own web API](https://github.com/Azure-Samples/active-directory-dotnetcore-daemon-v2/tree/master/4-Call-OwnApi-Pop) <br/> &#8226; [Using managed identity and Azure key vault](https://github.com/Azure-Samples/active-directory-dotnetcore-daemon-v2/tree/master/3-Using-KeyVault)| MSAL.NET | Client credentials grant|
109109
> | ASP.NET|[Multi-tenant with Microsoft identity platform endpoint](https://github.com/Azure-Samples/ms-identity-aspnet-daemon-webapp) | MSAL.NET | Client credentials grant|
110110
> | Java | &#8226; [Call Microsoft Graph with Secret](https://github.com/Azure-Samples/ms-identity-msal-java-samples/tree/main/1.%20Server-Side%20Scenarios/msal-client-credential-secret) <br/> &#8226; [Call Microsoft Graph with Certificate](https://github.com/Azure-Samples/ms-identity-msal-java-samples/tree/main/1.%20Server-Side%20Scenarios/msal-client-credential-certificate)| MSAL Java | Client credentials grant|
111-
> | Node.js | [Sign in users and call web API](https://github.com/Azure-Samples/ms-identity-javascript-nodejs-console) | MSAL Node | Client credentials grant |
111+
> | Node.js | [Call Microsoft Graph with secret](https://github.com/Azure-Samples/ms-identity-javascript-nodejs-console) | MSAL Node | Client credentials grant |
112112
> | Python | &#8226; [Call Microsoft Graph with secret](https://github.com/Azure-Samples/ms-identity-python-daemon/tree/master/1-Call-MsGraph-WithSecret) <br/> &#8226; [Call Microsoft Graph with certificate](https://github.com/Azure-Samples/ms-identity-python-daemon/tree/master/2-Call-MsGraph-WithCertificate) | MSAL Python| Client credentials grant|
113113
114114
## Azure Functions as web APIs

articles/active-directory/develop/scenario-protected-web-api-app-configuration.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -117,7 +117,7 @@ You can create a web API from scratch by using Microsoft.Identity.Web project te
117117

118118
#### Starting from an existing ASP.NET Core 3.1 application
119119

120-
ASP.NET Core 3.1 uses the Microsoft.AspNetCore.AzureAD.UI library. The middleware is initialized in the Startup.cs file.
120+
ASP.NET Core 3.1 uses the Microsoft.AspNetCore.Authentication.JwtBearer library. The middleware is initialized in the Startup.cs file.
121121

122122
```csharp
123123
using Microsoft.AspNetCore.Authentication.JwtBearer;

0 commit comments

Comments
 (0)