Skip to content

Commit e9300b6

Browse files
committed
Merge branch 'main' into release-preview-acss
2 parents e72a91b + 083efcb commit e9300b6

File tree

244 files changed

+1827
-868
lines changed

Some content is hidden

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

244 files changed

+1827
-868
lines changed

.openpublishing.redirection.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,10 @@
11
{
22
"redirections": [
3+
{
4+
"source_path": "articles/api-management/zone-redundancy.md",
5+
"redirect_url": "/azure/availability-zones/migrate-api-mgt",
6+
"redirect_document_id": false
7+
},
38
{
49
"source_path": "articles/virtual-machines/linux/find-unattached-nics.md",
510
"redirect_url": "/previous-versions/azure/virtual-machines/linux/find-unattached-nics",

articles/active-directory-b2c/error-codes.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ manager: CelesteDG
99
ms.service: active-directory
1010
ms.workload: identity
1111
ms.topic: reference
12-
ms.date: 06/16/2021
12+
ms.date: 07/18/2022
1313
ms.author: kengaderdus
1414
ms.subservice: B2C
1515
---
@@ -20,6 +20,7 @@ The following errors can be returned by the Azure Active Directory B2C service.
2020

2121
| Error code | Message | Notes |
2222
| ---------- | ------- | ----- |
23+
| `AADB2C90001` | This user already exists, and profile '{0}' does not allow the same user to be created again. | [Sign-up flow](add-sign-up-and-sign-in-policy.md) |
2324
| `AADB2C90002` | The CORS resource '{0}' returned a 404 not found. | [Hosting the page content](customize-ui-with-html.md#hosting-the-page-content) |
2425
| `AADB2C90006` | The redirect URI '{0}' provided in the request is not registered for the client ID '{1}'. | [Register a web application](tutorial-register-applications.md), [Sending authentication requests](openid-connect.md#send-authentication-requests) |
2526
| `AADB2C90007` | The application associated with client ID '{0}' has no registered redirect URIs. | [Register a web application](tutorial-register-applications.md), [Sending authentication requests](openid-connect.md#send-authentication-requests) |
41.2 KB
Loading
26.8 KB
Loading

articles/active-directory/app-provisioning/partner-driven-integrations.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ manager: rkarlin
77
ms.service: active-directory
88
ms.workload: identity
99
ms.topic: overview
10-
ms.date: 07/08/2022
10+
ms.date: 07/18/2022
1111
ms.subservice: hybrid
1212
ms.author: billmath
1313
ms.collection: M365-identity-device-management
@@ -22,12 +22,16 @@ Popular third party applications, such as Dropbox, Snowflake, and Workplace by F
2222
**Option 2 - Implement a SCIM compliant API for your application:**
2323
If your line-of-business application supports the [SCIM](https://aka.ms/scimoverview) standard, it can easily be integrated with the [Azure AD SCIM client](use-scim-to-provision-users-and-groups.md).
2424

25+
[![Diagram showing implementation of a SCIM compliant API for your application.](media/partner-driven-integrations/scim-compliant-api-1.png)](media/partner-driven-integrations/scim-compliant-api-1.png#lightbox)
26+
2527
**Option 3 - Use Microsoft Graph:**
2628
Many new applications use Microsoft Graph to retrieve users, groups and other resources from Azure Active Directory. You can learn more about what scenarios to use [SCIM and Graph](scim-graph-scenarios.md) in.
2729

2830
**Option 4 - Use partner-driven connectors:**
2931
In cases where an application doesn't support SCIM, partners have built gateways between the Azure AD SCIM client and target applications. **This document serves as a place for partners to attest to integrations that are compatible with Azure Active Directory, and for customers to discover these partner-driven integrations.** These gateways are built, maintained, and owned by the third-party vendor.
3032

33+
[![Diagram showing gateways between the Azure AD SCIM client and target applications.](media/partner-driven-integrations/partner-driven-connectors-1.png)](media/partner-driven-integrations/partner-driven-connectors-1.png#lightbox)
34+
3135
## Available partner-driven integrations
3236
The descriptions and lists of applications below are provided by the partners themselves. You can use the lists of applications supported to identify a partner that you may want to contact and learn more about.
3337

articles/active-directory/devices/device-management-azure-portal.md

Lines changed: 14 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -6,12 +6,12 @@ services: active-directory
66
ms.service: active-directory
77
ms.subservice: devices
88
ms.topic: how-to
9-
ms.date: 05/06/2022
9+
ms.date: 07/18/2022
1010

1111
ms.author: joflore
1212
author: MicrosoftGuyJFlo
1313
manager: karenhoran
14-
ms.reviewer: hafowler
14+
ms.reviewer: myra-ramdenbourg
1515

1616
ms.collection: M365-identity-device-management
1717
---
@@ -107,26 +107,30 @@ To view or copy BitLocker keys, you need to be the owner of the device or have o
107107
- Security Administrator
108108
- Security Reader
109109

110-
## Device-list filtering (preview)
110+
## View and filter your devices (preview)
111111

112-
Previously, you could filter the device list only by activity and enabled state. In this preview, you can filter the device list by these device attributes:
112+
In this preview, you have the ability to infinitely scroll, reorder columns, and select all devices. You can filter the device list by these device attributes:
113113

114114
- Enabled state
115115
- Compliant state
116116
- Join type (Azure AD joined, Hybrid Azure AD joined, Azure AD registered)
117117
- Activity timestamp
118118
- OS
119119
- Device type (printer, secure VM, shared device, registered device)
120+
- MDM
121+
- Extension attributes
122+
- Administrative unit
123+
- Owner
120124

121-
To enable the preview filtering functionality in the **All devices** view:
125+
To enable the preview in the **All devices** view:
122126

123127
1. Sign in to the [Azure portal](https://portal.azure.com).
124-
1. Go to **Azure Active Directory** > **Devices**.
125-
1. Select the banner that says **Try out the new devices filtering improvements. Click to enable the preview.**
126-
127-
![Enable filtering preview functionality](./media/device-management-azure-portal/device-filter-preview-enable.png)
128+
2. Go to **Azure Active Directory** > **Devices** > **All devices**.
129+
3. Select the **Preview features** button.
130+
4. Turn on the toggle that says **Enhanced devices list experience**. Select **Apply**.
131+
5. Refresh your browser.
128132

129-
You can now add filters to your **All devices** view.
133+
You can now experience the enhanced **All devices** view.
130134

131135
## Download devices
132136

articles/active-directory/fundamentals/whats-new-archive.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3770,7 +3770,7 @@ Because of modern browser [3rd party cookie restrictions such as Safari ITP](../
37703770
**Service category:** Device Management
37713771
**Product capability:** Device Lifecycle Management
37723772

3773-
Previously, the only filters you could use were "Enabled" and "Activity date." Now, you can [filter your list of devices on more properties](../devices/device-management-azure-portal.md#device-list-filtering-preview), including OS type, join type, compliance, and more. These additions should simplify locating a particular device.
3773+
Previously, the only filters you could use were "Enabled" and "Activity date." Now, you can [filter your list of devices on more properties](../devices/device-management-azure-portal.md), including OS type, join type, compliance, and more. These additions should simplify locating a particular device.
37743774

37753775
---
37763776

articles/active-directory/manage-apps/tutorial-manage-access-security.md

Lines changed: 13 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.author: jomondi
77
ms.service: active-directory
88
ms.subservice: app-mgmt
99
ms.topic: tutorial
10-
ms.date: 02/24/2022
10+
ms.date: 07/18/2022
1111

1212
# Customer intent: As an administrator of an Azure AD tenant, I want to manage access to my applications and make sure they are secure.
1313
---
@@ -76,7 +76,7 @@ In this tutorial, the administrator can find the basic steps to configure the ap
7676
1. Set **Enable policy** to **On**.
7777
1. To apply the Conditional Access policy, select **Create**.
7878

79-
## Test multi-factor authentication
79+
### Test multi-factor authentication
8080

8181
1. Open a new browser window in InPrivate or incognito mode and browse to the URL of the application.
8282
1. Sign in with the user account that you assigned to the application. You're required to register for and use Azure AD Multi-Factor Authentication. Follow the prompts to complete the process and verify you successfully sign into the Azure portal.
@@ -98,10 +98,10 @@ Juan wants to make sure that certain terms and conditions are known to users bef
9898
1. For **Enforce with conditional access policy templates**, select **Custom policy**.
9999
1. Select **Create**.
100100

101-
## Add the terms of use to the policy
101+
### Add the terms of use to the policy
102102

103103
1. In the left menu of the tenant overview, select **Security**.
104-
1. Select **Conditional Access**, and then select the *MFA Pilot* policy.
104+
1. Select **Conditional Access**, and then **Policies**. From the list of policies, select the *MFA Pilot* policy.
105105
1. Under **Access controls** and **Grant**, select the controls selected link.
106106
1. Select *My TOU*.
107107
1. Select **Require all the selected controls**, and then choose **Select**.
@@ -114,6 +114,8 @@ The My Apps portal enables administrators and users to manage the applications u
114114
> [!NOTE]
115115
> Applications only appear in a user's my Apps portal after the user is assigned to the application and the application is configured to be visible to users. See [Configure application properties](add-application-portal-configure.md) to learn how to make the application visible to users.
116116
117+
By default, all applications are listed together on a single page. But you can use collections to group together related applications and present them on a separate tab, making them easier to find. For example, you can use collections to create logical groupings of applications for specific job roles, tasks, projects, and so on. In this section, you create a collection and assign it to users and groups.
118+
117119
1. Open the Azure portal.
118120
1. Go to **Azure Active Directory**, and then select **Enterprise Applications**.
119121
1. Under **Manage**, select **Collections**.
@@ -124,6 +126,13 @@ The My Apps portal enables administrators and users to manage the applications u
124126
1. Select the **Users and groups** tab. Select **+ Add users and groups**, and then in the **Add users and groups** page, select the users or groups you want to assign the collection to. Or use the Search box to find users or groups. When you're finished selecting users and groups, choose **Select**.
125127
1. Select **Review + Create**, and then select **Create**. The properties for the new collection appear.
126128

129+
### Check the collection in the My Apps portal
130+
131+
1. Open a new browser window in InPrivate or incognito mode and browse to the [My Apps](https://myapps.microsoft.com/) portal.
132+
1. Sign in with the user account that you assigned to the application.
133+
1. Check that the collection you created appears in the My Apps portal.
134+
1. Close the browser window.
135+
127136
## Clean up resources
128137

129138
You can keep the resources for future use, or if you're not going to continue to use the resources created in this tutorial, delete them with the following steps.

articles/active-directory/verifiable-credentials/introduction-to-verifiable-credentials-architecture.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,13 +2,13 @@
22
title: Azure Active Directory architecture overview (preview)
33
description: Learn foundational information to plan and design your solution
44
documentationCenter: ''
5-
author: barbaraselden
5+
author: barclayn
66
manager: martinco
77
ms.service: decentralized-identity
88
ms.topic: how-to
99
ms.subservice: verifiable-credentials
1010
ms.date: 06/02/2022
11-
ms.author: baselden
11+
ms.author: barclayn
1212
---
1313

1414
# Azure AD Verifiable Credentials architecture overview (preview)

articles/active-directory/verifiable-credentials/plan-issuance-solution.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,13 +2,13 @@
22
title: Plan your Azure Active Directory Verifiable Credentials issuance solution(preview)
33
description: Learn to plan your end-to-end issuance solution.
44
documentationCenter: ''
5-
author: barbaraselden
5+
author: barclayn
66
manager: martinco
77
ms.service: decentralized-identity
88
ms.topic: how-to
99
ms.subservice: verifiable-credentials
1010
ms.date: 06/03/2022
11-
ms.author: baselden
11+
ms.author: barclayn
1212
ms.custom: references_regions
1313
---
1414

0 commit comments

Comments
 (0)