Skip to content

Commit b96199b

Browse files
author
Ryan Willis
committed
Merge branch 'main' of github.com:MicrosoftDocs/azure-docs-pr into arc-server-vdi
2 parents 124fd7c + 134100b commit b96199b

File tree

1,231 files changed

+10750
-10965
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,231 files changed

+10750
-10965
lines changed

.openpublishing.publish.config.json

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -987,6 +987,7 @@
987987
"articles/iot-fundamentals/.openpublishing.redirection.iot-fundamentals.json",
988988
"articles/iot-hub/.openpublishing.redirection.iot-hub.json",
989989
"articles/load-testing/.openpublishing.redirection.azure-load-testing.json",
990+
"articles/logic-apps/.openpublishing.redirection.logic-apps.json",
990991
"articles/machine-learning/.openpublishing.redirection.machine-learning.json",
991992
"articles/mariadb/.openpublishing.redirection.mariadb.json",
992993
"articles/marketplace/.openpublishing.redirection.marketplace.json",

.openpublishing.redirection.json

Lines changed: 10 additions & 746 deletions
Large diffs are not rendered by default.

articles/active-directory-b2c/integrate-with-app-code-samples.md

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -2,11 +2,11 @@
22
title: Azure Active Directory B2C integrate with app samples
33
description: Code samples for integrating Azure AD B2C to mobile, desktop, web, and single-page applications.
44
services: active-directory-b2c
5-
author: kengaderdus
5+
author: garrodonnell
66
manager: CelesteDG
77

8-
ms.author: kengaderdus
9-
ms.date: 06/21/2022
8+
ms.author: godonnell
9+
ms.date: 02/21/2023
1010
ms.custom: mvc
1111
ms.topic: sample
1212
ms.service: active-directory
@@ -17,17 +17,6 @@ ms.subservice: B2C
1717

1818
The following tables provide links to samples for applications including iOS, Android, .NET, and Node.js.
1919

20-
## Mobile and desktop apps
21-
22-
| Sample | Description |
23-
|--------| ----------- |
24-
| [ios-swift-native-msal](https://github.com/Azure-Samples/active-directory-b2c-ios-swift-native-msal) | An iOS sample in Swift that authenticates Azure AD B2C users and calls an API using OAuth 2.0 |
25-
| [android-native-msal](https://github.com/Azure-Samples/ms-identity-android-java#b2cmodefragment-class) | A simple Android app showcasing how to use MSAL to authenticate users via Azure Active Directory B2C, and access a Web API with the resulting tokens. |
26-
| [ios-native-appauth](https://github.com/Azure-Samples/active-directory-b2c-ios-native-appauth) | A sample that shows how you can use a third-party library to build an iOS application in Objective-C that authenticates Microsoft identity users to our Azure AD B2C identity service. |
27-
| [android-native-appauth](https://github.com/Azure-Samples/active-directory-b2c-android-native-appauth) | A sample that shows how you can use a third-party library to build an Android application that authenticates Microsoft identity users to our B2C identity service and calls a web API using OAuth 2.0 access tokens. |
28-
| [dotnet-desktop](https://github.com/Azure-Samples/active-directory-b2c-dotnet-desktop) | A sample that shows how a Windows Desktop .NET (WPF) application can sign in a user using Azure AD B2C, get an access token using MSAL.NET and call an API. |
29-
| [xamarin-native](https://github.com/Azure-Samples/active-directory-b2c-xamarin-native) | A simple Xamarin Forms app showcasing how to use MSAL to authenticate users via Azure Active Directory B2C, and access a Web API with the resulting tokens. |
30-
3120
## Web apps and APIs
3221

3322
| Sample | Description |
@@ -48,6 +37,17 @@ The following tables provide links to samples for applications including iOS, An
4837
| [ms-identity-b2c-javascript-spa](https://github.com/Azure-Samples/ms-identity-b2c-javascript-spa) | A VanillaJS single page application (SPA) calling a web API. Authentication is done with Azure AD B2C by using MSAL.js. This sample uses the authorization code flow with PKCE. |
4938
| [javascript-nodejs-management](https://github.com/Azure-Samples/ms-identity-b2c-javascript-nodejs-management/tree/main/Chapter1) | A VanillaJS single page application (SPA) calling Microsoft Graph to manage users in a B2C directory. Authentication is done with Azure AD B2C by using MSAL.js. This sample uses the authorization code flow with PKCE.|
5039

40+
## Mobile and desktop apps
41+
42+
| Sample | Description |
43+
|--------| ----------- |
44+
| [ios-swift-native-msal](https://github.com/Azure-Samples/active-directory-b2c-ios-swift-native-msal) | An iOS sample in Swift that authenticates Azure AD B2C users and calls an API using OAuth 2.0 |
45+
| [android-native-msal](https://github.com/Azure-Samples/ms-identity-android-java#b2cmodefragment-class) | A simple Android app showcasing how to use MSAL to authenticate users via Azure Active Directory B2C, and access a Web API with the resulting tokens. |
46+
| [ios-native-appauth](https://github.com/Azure-Samples/active-directory-b2c-ios-native-appauth) | A sample that shows how you can use a third-party library to build an iOS application in Objective-C that authenticates Microsoft identity users to our Azure AD B2C identity service. |
47+
| [android-native-appauth](https://github.com/Azure-Samples/active-directory-b2c-android-native-appauth) | A sample that shows how you can use a third-party library to build an Android application that authenticates Microsoft identity users to our B2C identity service and calls a web API using OAuth 2.0 access tokens. |
48+
| [dotnet-desktop](https://github.com/Azure-Samples/active-directory-b2c-dotnet-desktop) | A sample that shows how a Windows Desktop .NET (WPF) application can sign in a user using Azure AD B2C, get an access token using MSAL.NET and call an API. |
49+
| [xamarin-native](https://github.com/Azure-Samples/active-directory-b2c-xamarin-native) | A simple Xamarin Forms app showcasing how to use MSAL to authenticate users via Azure Active Directory B2C, and access a Web API with the resulting tokens. |
50+
5151
## Console/Daemon apps
5252

5353
| Sample | Description |

articles/active-directory-b2c/technical-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ The primary resources you work with in an Azure AD B2C tenant are:
3838
An Azure AD B2C tenant is the first resource you need to create to get started with Azure AD B2C. Learn how to:
3939

4040
* [Create an Azure Active Directory B2C tenant](tutorial-create-tenant.md).
41-
* [Manage your Azure AD B2C tenant](tenant-management.md)
41+
* [Manage your Azure AD B2C tenant](tenant-management-manage-administrator.md)
4242

4343
## Accounts in Azure AD B2C
4444

articles/active-directory-b2c/user-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ In Azure Active Directory B2C (Azure AD B2C), there are several types of account
2121
The following types of accounts are available:
2222

2323
- **Work account** - A work account can access resources in a tenant, and with an administrator role, can manage tenants.
24-
- **Guest account** - A guest account can only be a Microsoft account or an Azure AD user that can be used to share administration responsibilities such as [managing a tenant](tenant-management.md).
24+
- **Guest account** - A guest account can only be a Microsoft account or an Azure AD user that can be used to share administration responsibilities such as [managing a tenant](tenant-management-manage-administrator.md).
2525
- **Consumer account** - A consumer account is used by a user of the applications you've registered with Azure AD B2C. Consumer accounts can be created by:
2626
- The user going through a sign-up user flow in an Azure AD B2C application
2727
- Using Microsoft Graph API

articles/active-directory-domain-services/policy-reference.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Built-in policy definitions for Azure Active Directory Domain Services
33
description: Lists Azure Policy built-in policy definitions for Azure Active Directory Domain Services. These built-in policy definitions provide common approaches to managing your Azure resources.
4-
ms.date: 01/29/2023
4+
ms.date: 02/21/2023
55
ms.service: active-directory
66
ms.subservice: domain-services
77
author: justinha

articles/active-directory/app-provisioning/use-scim-to-provision-users-and-groups.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.service: active-directory
88
ms.subservice: app-provisioning
99
ms.workload: identity
1010
ms.topic: tutorial
11-
ms.date: 11/04/2022
11+
ms.date: 02/22/2023
1212
ms.author: kenwith
1313
ms.reviewer: arvinh
1414
---
@@ -74,7 +74,7 @@ The following table lists an example of required attributes:
7474
|lastName|name.familyName|surName|
7575
|workMail|emails[type eq “work”].value|Mail|
7676
|manager|manager|manager|
77-
|tag|urn:ietf:params:scim:schemas:extension:CustomExtensionName:2.0:User:tag|extensionAttribute1|
77+
|tag|`urn:ietf:params:scim:schemas:extension:CustomExtensionName:2.0:User:tag`|extensionAttribute1|
7878
|status|active|isSoftDeleted (computed value not stored on user)|
7979

8080
The following JSON payload shows an example SCIM schema:
@@ -117,7 +117,7 @@ It helps to categorize between `/User` and `/Group` to map any default user attr
117117

118118
The following table lists an example of user attributes:
119119

120-
| Azure AD user | urn:ietf:params:scim:schemas:extension:enterprise:2.0:User |
120+
| Azure AD user | `urn:ietf:params:scim:schemas:extension:enterprise:2.0:User` |
121121
| --- | --- |
122122
| IsSoftDeleted |active |
123123
|department| `urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:department`|
@@ -140,7 +140,7 @@ The following table lists an example of user attributes:
140140

141141
The following table lists an example of group attributes:
142142

143-
| Azure AD group | urn:ietf:params:scim:schemas:core:2.0:Group |
143+
| Azure AD group | `urn:ietf:params:scim:schemas:core:2.0:Group` |
144144
| --- | --- |
145145
| displayName |displayName |
146146
| members |members |

articles/active-directory/app-provisioning/user-provisioning.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.service: active-directory
77
ms.subservice: app-provisioning
88
ms.topic: overview
99
ms.workload: identity
10-
ms.date: 02/17/2023
10+
ms.date: 02/21/2023
1111
ms.author: kenwith
1212
ms.reviewer: arvinh
1313
---
@@ -52,15 +52,15 @@ The provisioning mode supported by an application is also visible on the **Provi
5252

5353
## Benefits of automatic provisioning
5454

55-
The number of applications used in modern organizations continues to grow. IT admins must manage access management at scale. Admins use standards such as SAML or OIDC for single sign-on (SSO), but access also requires users to be provisioned into the app. To many admins, provisioning means manually creating every user account or uploading CSV files each week. These processes are time-consuming, expensive, and error prone. Solutions such as SAML just-in-time (JIT) have been adopted to automate provisioning. Enterprises also need a solution to deprovision users when they leave the organization or no longer require access to certain apps based on role change.
55+
The number of applications used in modern organizations continues to grow. You, as an IT admin, must manage access management at scale. You use standards such as SAML or OIDC for single sign-on (SSO), but access also requires you provision users into an app. You might think provisioning means manually creating every user account or uploading CSV files each week. These processes are time-consuming, expensive, and error prone. To streamline the process, use SAML just-in-time (JIT) to automate provisioning. Use the same process to deprovision users when they leave the organization or no longer require access to certain apps based on role change.
5656

5757
Some common motivations for using automatic provisioning include:
5858

5959
- Maximizing the efficiency and accuracy of provisioning processes.
6060
- Saving on costs associated with hosting and maintaining custom-developed provisioning solutions and scripts.
6161
- Securing your organization by instantly removing users' identities from key SaaS apps when they leave the organization.
6262
- Easily importing a large number of users into a particular SaaS application or system.
63-
- Having a single set of policies to determine who is provisioned and who can sign in to an app.
63+
- A single set of policies to determine provisioned users that can sign in to an app.
6464

6565
Azure AD user provisioning can help address these challenges. To learn more about how customers have been using Azure AD user provisioning, read the [ASOS case study](https://aka.ms/asoscasestudy). The following video provides an overview of user provisioning in Azure AD.
6666

@@ -74,7 +74,7 @@ Azure AD features pre-integrated support for many popular SaaS apps and human re
7474

7575
![Image that shows logos for DropBox, Salesforce, and others.](./media/user-provisioning/gallery-app-logos.png)
7676

77-
If you want to request a new application for provisioning, you can [request that your application be integrated with our app gallery](../manage-apps/v2-howto-app-gallery-listing.md). For a user provisioning request, we require the application to have a SCIM-compliant endpoint. Request that the application vendor follows the SCIM standard so we can onboard the app to our platform quickly.
77+
To request a new application for provisioning, see [Submit a request to publish your application in Azure Active Directory application gallery](../manage-apps/v2-howto-app-gallery-listing.md). For a user provisioning request, we require the application to have a SCIM-compliant endpoint. Request that the application vendor follows the SCIM standard so we can onboard the app to our platform quickly.
7878

7979
* **Applications that support SCIM 2.0**: For information on how to generically connect applications that implement SCIM 2.0-based user management APIs, see [Build a SCIM endpoint and configure user provisioning](use-scim-to-provision-users-and-groups.md).
8080

articles/active-directory/authentication/concept-authentication-default-enablement.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ Number matching is a good example of protection for an authentication method tha
3737
As MFA fatigue attacks rise, number matching becomes more critical to sign-in security. As a result, Microsoft will change the default behavior for push notifications in Microsoft Authenticator.
3838

3939
>[!NOTE]
40-
>Number matching will begin to be enabled for all users of Microsoft Authenticator starting February 27, 2023.
40+
>Number matching will begin to be enabled for all users of Microsoft Authenticator starting May 08, 2023.
4141
4242
<!---Add link to Mayur Blog post here--->
4343

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

Lines changed: 27 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -72,9 +72,35 @@ 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+
## Certificate-based authentication is MFA capable
76+
77+
Azure AD CBA is an MFA (Multi factor authentication) capable method, that is Azure AD CBA can be either Single (SF) or Multi-factor (MF) depending on the tenant configuration. Enabling CBA for a user indicates the user is potentially capable of MFA. This means a user may need additional configuration to get MFA and proof up to register other authentication methods when the user is in scope for CBA.
78+
79+
If CBA enabled user only has a Single Factor (SF) certificate and need MFA
80+
1. Use Password + SF certificate.
81+
1. Issue Temporary Access Pass (TAP)
82+
1. Admin adds Phone Number to user account and allows Voice/SMS method for user.
83+
84+
If CBA enabled user has not yet been issued a certificate and need MFA
85+
1. Issue Temporary Access Pass (TAP)
86+
1. Admin adds Phone Number to user account and allows Voice/SMS method for user.
87+
88+
If CBA enabled user cannot use MF cert (such as on mobile device without smart card support) and need MFA
89+
1. Issue Temporary Access Pass (TAP)
90+
1. User Register another MFA method (when user can use MF cert)
91+
1. Use Password + MF cert (when user can use MF cert)
92+
1. Admin adds Phone Number to user account and allows Voice/SMS method for user
93+
94+
7595
## MFA with Single-factor certificate-based authentication
7696

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.
97+
Azure AD CBA can be used as a second factor to meet MFA requirements with single-factor certificates. The supported combintaions are
98+
99+
CBA (first factor) + passwordless phone sign-in (PSI as second factor)
100+
CBA (first factor) + FIDO2 security keys
101+
Password (first factor) + CBA (second factor)
102+
103+
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.
78104

79105
>[!IMPORTANT]
80106
>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)

0 commit comments

Comments
 (0)