Skip to content

Commit d10617c

Browse files
Tyler WhitneyTyler Whitney
authored andcommitted
merge master
2 parents ed22e2e + b515852 commit d10617c

File tree

313 files changed

+1771
-982
lines changed

Some content is hidden

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

313 files changed

+1771
-982
lines changed

.openpublishing.redirection.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10037,6 +10037,11 @@
1003710037
"redirect_url": "/azure-stack/user/azure-stack-vpn-gateway-about-vpn-gateways",
1003810038
"redirect_document_id": false
1003910039
},
10040+
{
10041+
"source_path": "articles/virtual-wan/virtual-wan-office365-overview.md",
10042+
"redirect_url": "/azure/virtual-wan/virtual-wan-about",
10043+
"redirect_document_id": false
10044+
},
1004010045
{
1004110046
"source_path": "articles/azure-stack/azure-stack-vpn-gateway-settings.md",
1004210047
"redirect_url": "/azure-stack/user/azure-stack-vpn-gateway-settings",

articles/active-directory-b2c/active-directory-b2c-devquickstarts-graph-dotnet.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -360,6 +360,5 @@ By using `B2CGraphClient`, you have a service application that can manage your B
360360
As you incorporate this functionality into your own application, remember a few key points for B2C applications:
361361

362362
* Grant the application the required permissions in the tenant.
363-
* For now, you need to use ADAL (not MSAL) to get access tokens. (You can also send protocol messages directly, without using a library.)
364363
* When you call the Graph API, use `api-version=1.6`.
365364
* When you create and update consumer users, a few properties are required, as described above.

articles/active-directory-b2c/b2clogin.md

Lines changed: 22 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Set redirect URLs to b2clogin.com - Azure Active Directory B2C
2+
title: Migrate applications and APIs to b2clogin.com - Azure AD B2C
33
description: Learn about using b2clogin.com in your redirect URLs for Azure Active Directory B2C.
44
services: active-directory-b2c
55
author: mmacy
@@ -8,7 +8,7 @@ manager: celestedg
88
ms.service: active-directory
99
ms.workload: identity
1010
ms.topic: conceptual
11-
ms.date: 08/17/2019
11+
ms.date: 12/04/2019
1212
ms.author: marsma
1313
ms.subservice: B2C
1414
---
@@ -17,6 +17,16 @@ ms.subservice: B2C
1717

1818
When you set up an identity provider for sign-up and sign-in in your Azure Active Directory B2C (Azure AD B2C) application, you need to specify a redirect URL. You should no longer reference *login.microsoftonline.com* in your applications and APIs. Instead, use *b2clogin.com* for all new applications, and migrate existing applications from *login.microsoftonline.com* to *b2clogin.com*.
1919

20+
## Deprecation of login.microsoftonline.com
21+
22+
On 04 December 2019, we announced the scheduled retirement of login.microsoftonline.com support in Azure AD B2C on **04 December 2020**:
23+
24+
[Azure Active Directory B2C is deprecating login.microsoftonline.com](https://azure.microsoft.com/updates/b2c-deprecate-msol/)
25+
26+
The deprecation of login.microsoftonline.com goes into effect for all Azure AD B2C tenants on 04 December 2020, providing existing tenants one (1) year to migrate to b2clogin.com. New tenants created after 04 December 2019 will not accept requests from login.microsoftonline.com. All functionality remains the same on the b2clogin.com endpoint.
27+
28+
The deprecation of login.microsoftonline.com does not impact Azure Active Directory tenants. Only Azure Active Directory B2C tenants are affected by this change.
29+
2030
## Benefits of b2clogin.com
2131

2232
When you use *b2clogin.com* as your redirect URL:
@@ -68,6 +78,10 @@ For example, the authority endpoint for Contoso's sign-up/sign-in policy would n
6878
https://contosob2c.b2clogin.com/00000000-0000-0000-0000-000000000000/B2C_1_signupsignin1
6979
```
7080

81+
For information about migrating OWIN-based web applications to b2clogin.com, see [Migrate an OWIN-based web API to b2clogin.com](multiple-token-endpoints.md).
82+
83+
For migrating Azure API Management APIs protected by Azure AD B2C, see the [Migrate to b2clogin.com](secure-api-management.md#migrate-to-b2clogincom) section of [Secure an Azure API Management API with Azure AD B2C](secure-api-management.md).
84+
7185
## Microsoft Authentication Library (MSAL)
7286

7387
### ValidateAuthority property
@@ -92,6 +106,12 @@ this.clientApplication = new UserAgentApplication(
92106
);
93107
```
94108

109+
## Next steps
110+
111+
For information about migrating OWIN-based web applications to b2clogin.com, see [Migrate an OWIN-based web API to b2clogin.com](multiple-token-endpoints.md).
112+
113+
For migrating Azure API Management APIs protected by Azure AD B2C, see the [Migrate to b2clogin.com](secure-api-management.md#migrate-to-b2clogincom) section of [Secure an Azure API Management API with Azure AD B2C](secure-api-management.md).
114+
95115
<!-- LINKS - External -->
96116
[msal-dotnet]: https://github.com/AzureAD/microsoft-authentication-library-for-dotnet
97117
[msal-dotnet-b2c]: https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/wiki/AAD-B2C-specifics

articles/active-directory/cloud-provisioning/what-is-cloud-provisioning.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ With Azure AD Connect cloud provisioning, provisioning from AD to Azure AD is or
2929

3030
The following table provides a comparison between Azure AD Connect and Azure AD Connect cloud provisioning:
3131

32-
| Feature | Azure Active Directory Connect synch| Azure Active Directory Connect cloud provisioning |
32+
| Feature | Azure Active Directory Connect sync| Azure Active Directory Connect cloud provisioning |
3333
|:--- |:---:|:---:|
3434
|Connect to single on-premises AD forest|||
3535
| Connect to multiple on-premises AD forests |||

articles/active-directory/conditional-access/TOC.yml

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -64,8 +64,6 @@
6464
href: howto-conditional-access-policy-compliant-device.md
6565
- name: Block legacy authentication
6666
href: block-legacy-authentication.md
67-
- name: Conditional Access for MFA registration
68-
href: ../authentication/howto-registration-mfa-sspr-combined.md#conditional-access-policies-for-combined-registration
6967
- name: Require approved client apps
7068
href: app-based-conditional-access.md
7169
- name: Require app protection policy

articles/active-directory/conditional-access/howto-conditional-access-policy-registration.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ ms.collection: M365-identity-device-management
1717
---
1818
# Conditional Access: Require trusted location for MFA registration
1919

20-
Securing when and how users register for Azure Multi-Factor Authentication and self-service password reset is now possible with user actions in Conditional Access policy. This preview feature is available to organizations who have enabled the [combined registration preview](../authentication/concept-registration-mfa-sspr-combined.md). This functionality may be enabled in organizations where they want users to register for Azure Multi-Factor Authentication and SSPR from a central location such as a trusted network location during HR onboarding. For more information about creating trusted locations in Conditional Access, see the article [What is the location condition in Azure Active Directory Conditional Access?](../conditional-access/location-condition.md#named-locations)
20+
Securing when and how users register for Azure Multi-Factor Authentication and self-service password reset is now possible with user actions in Conditional Access policy. This preview feature is available to organizations who have enabled the [combined registration preview](../authentication/concept-registration-mfa-sspr-combined.md). This functionality may be enabled in organizations where they want to use conditions like trusted network location to restrict access to register for Azure Multi-Factor Authentication and SSPR. For more information about creating trusted locations in Conditional Access, see the article [What is the location condition in Azure Active Directory Conditional Access?](../conditional-access/location-condition.md#named-locations)
2121

2222
## Create a policy to require registration from a trusted location
2323

articles/active-directory/develop/config-authority.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Configure MSAL for iOS and macOS to use different identity providers
2+
title: Configure different identity providers (MSAL iOS/macOS) | Azure
33
titleSuffix: Microsoft identity platform
44
description: Learn how to use different authorities such as B2C, sovereign clouds, and guest users, with MSAL for iOS and macOS.
55
services: active-directory

articles/active-directory/develop/howto-add-app-roles-in-azure-ad-apps.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Add app roles in your Azure Active Directory-registered app and receive them in the token
2+
title: Add app roles and get them from a token | Azure
33
titleSuffix: Microsoft identity platform
44
description: Learn how to add app roles in an application registered in Azure Active Directory, assign users and groups to these roles and receive them in the `roles` claim in the token.
55
services: active-directory

articles/active-directory/develop/msal-configuration.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Understand the Android Microsoft Authentication Library (MSAL) configuration file
2+
title: Android Microsoft Authentication Library config file | Azure
33
titleSuffix: Microsoft identity platform
44
description: An overview of the Android Microsoft Authentication Library (MSAL) configuration file, which represents an application's configuration in Azure Active Directory.
55
services: active-directory
@@ -20,9 +20,9 @@ ms.reviewer: shoatman
2020
ms.collection: M365-identity-device-management
2121
---
2222

23-
# Android Microsoft Authentication Library (MSAL) configuration file
23+
# Android Microsoft Authentication Library configuration file
2424

25-
MSAL ships with a [default configuration JSON file](https://github.com/AzureAD/microsoft-authentication-library-for-android/blob/dev/msal/src/main/res/raw/msal_default_config.json) that you customize to define the behavior of your public client app for things such as the default authority, which authorities you'll use, and so on.
25+
The Android Microsoft Authentication Library (MSAL) ships with a [default configuration JSON file](https://github.com/AzureAD/microsoft-authentication-library-for-android/blob/dev/msal/src/main/res/raw/msal_default_config.json) that you customize to define the behavior of your public client app for things such as the default authority, which authorities you'll use, and so on.
2626

2727
This article will help you understand the various settings in the configuration file and how to specify the configuration file to use in your MSAL-based app.
2828

articles/active-directory/develop/msal-js-avoid-page-reloads.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Avoid page reloads (MSAL.js)
2+
title: Avoid page reloads (MSAL.js) | Azure
33
titleSuffix: Microsoft identity platform
44
description: Learn how to avoid page reloads when acquiring and renewing tokens silently using the Microsoft Authentication Library for JavaScript (MSAL.js).
55
services: active-directory

0 commit comments

Comments
 (0)