Skip to content

Commit 656827a

Browse files
memildinmemildin
committed
Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into asc-melvyn-release-notes
2 parents 69609c5 + 91167d7 commit 656827a

File tree

487 files changed

+9043
-3510
lines changed

Some content is hidden

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

487 files changed

+9043
-3510
lines changed

‎.openpublishing.redirection.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -28138,6 +28138,11 @@
2813828138
"redirect_url": "/azure/storage/blobs/access-tiers-overview",
2813928139
"redirect_document_id": true
2814028140
},
28141+
{
28142+
"source_path_from_root": "/articles/storage/common/storage-auth-aad-msi.md",
28143+
"redirect_url": "/azure/storage/blobs/authorize-managed-identity",
28144+
"redirect_document_id": false
28145+
},
2814128146
{
2814228147
"source_path_from_root": "/articles/storage/storage-c-plus-plus-how-to-use-blobs.md",
2814328148
"redirect_url": "/azure/storage/blobs/storage-c-plus-plus-how-to-use-blobs",

‎CODEOWNERS

Lines changed: 14 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -10,19 +10,20 @@
1010
/includes/policy/ @DCtheGeek
1111

1212
# Azure Monitor
13-
/articles/azure-monitor/* @bwren
14-
/articles/azure-monitor/agents @bwren
15-
/articles/azure-monitor/alerts @rboucher
16-
/articles/azure-monitor/app @bwren @lgayhardt
17-
/articles/azure-monitor/autoscale @rboucher
18-
/articles/azure-monitor/containers @bwren
19-
/articles/azure-monitor/essentials @bwren @rboucher
20-
/articles/azure-monitor/insights @bwren @rboucher @lgayhardt
21-
/articles/azure-monitor/logs @bwren
22-
/articles/azure-monitor/visualize @bwren @lgayhardt
23-
/articles/azure-monitor/vm @bwren
24-
/articles/advisor @rboucher
25-
/articles/service-health @rboucher
13+
articles/azure-monitor/* @bwren
14+
articles/azure-monitor/agents @bwren
15+
articles/azure-monitor/alerts @rboucher @abbyMSFT
16+
articles/azure-monitor/app @bwren
17+
articles/azure-monitor/autoscale @rboucher
18+
articles/azure-monitor/containers @bwren
19+
articles/azure-monitor/essentials @bwren @rboucher
20+
articles/azure-monitor/insights @bwren @rboucher
21+
articles/azure-monitor/logs @bwren @abbyMSFT
22+
articles/azure-monitor/visualize @bwren @rboucher
23+
articles/azure-monitor/vm @bwren
24+
articles/advisor @rboucher
25+
articles/service-health @rboucher
26+
2627

2728
# Azure Active Directory
2829
/articles/active-directory-b2c/ @msmimart @yoelhor

‎articles/active-directory-b2c/add-password-reset-policy.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -144,6 +144,7 @@ A claims transformation technical profile initiates the **isForgotPassword** cla
144144
<OutputClaims>
145145
<OutputClaim ClaimTypeReferenceId="isForgotPassword" DefaultValue="true" AlwaysUseDefaultValue="true"/>
146146
</OutputClaims>
147+
<UseTechnicalProfileForSessionManagement ReferenceId="SM-Noop" />
147148
</TechnicalProfile>
148149
<TechnicalProfile Id="SelfAsserted-LocalAccountSignin-Email">
149150
<Metadata>

‎articles/active-directory-b2c/deploy-custom-policies-devops.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -172,13 +172,13 @@ A pipeline task is a pre-packaged script that performs an action. Add a task tha
172172

173173

174174
```PowerShell
175-
-ClientID $(clientId) -ClientSecret $(clientSecret) -TenantId $(tenantId) -Folder $(System.DefaultWorkingDirectory)/policyRepo/B2CAssets/ -Files "TrustFrameworkBase.xml,TrustFrameworkExtensions.xml,SignUpOrSignin.xml,ProfileEdit.xml,PasswordReset.xml"
175+
-ClientID $(clientId) -ClientSecret $(clientSecret) -TenantId $(tenantId) -Folder $(System.DefaultWorkingDirectory)/policyRepo/B2CAssets/ -Files "TrustFrameworkBase.xml,TrustFrameworkLocalization.xml,TrustFrameworkExtensions.xml,SignUpOrSignin.xml,ProfileEdit.xml,PasswordReset.xml"
176176
```
177177
178178
The `-Files` parameter is a comma delimiter list of policy files to deploy. Update the list with your policy files.
179179
180180
> [!IMPORTANT]
181-
> Ensure the policies are uploaded in the correct order. First the base policy, the extensions policy, then the relying party policies. For example, `TrustFrameworkBase.xml,TrustFrameworkExtensions.xml,SignUpOrSignin.xml`.
181+
> Ensure the policies are uploaded in the correct order. First the base policy, the extensions policy, then the relying party policies. For example, `TrustFrameworkBase.xml,TrustFrameworkLocalization.xml,TrustFrameworkExtensions.xml,SignUpOrSignin.xml`.
182182
183183
1. Select **Save** to save the Agent job.
184184

‎articles/active-directory-b2c/deploy-custom-policies-github-action.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -94,7 +94,7 @@ To create a workflow, follow these steps:
9494
uses: azure-ad-b2c/deploy-trustframework-policy@v3
9595
with:
9696
folder: "./Policies"
97-
files: "TrustFrameworkBase.xml,TrustFrameworkExtensions.xml,SignUpOrSignin.xml"
97+
files: "TrustFrameworkBase.xml,TrustFrameworkLocalization.xml,TrustFrameworkExtensions.xml,SignUpOrSignin.xml"
9898
tenant: ${{ env.tenant }}
9999
clientId: ${{ env.clientId }}
100100
clientSecret: ${{ secrets.clientSecret }}
@@ -107,12 +107,13 @@ To create a workflow, follow these steps:
107107
| `env` | `clientId` | **Application (client) ID** of the application you registered in the [Register an MS Graph application](#register-a-microsoft-graph-application) step. |
108108
|`env`| `tenant` | Your Azure AD B2C [tenant name](tenant-management.md#get-your-tenant-name) (for example, contoso.onmicrosoft.com). |
109109
| `with`| `folder`| A folder where the custom policies files are stored, for example, `./Policies`.|
110-
| `with`| `files` | Comma-delimited list of policy files to deploy, for example, `TrustFrameworkBase.xml,TrustFrameworkExtensions.xml,SignUpOrSignin.xml`.|
110+
| `with`| `files` | Comma-delimited list of policy files to deploy, for example, `TrustFrameworkBase.xml,TrustFrameworkLocalization.xml,TrustFrameworkExtensions.xml,SignUpOrSignin.xml`.|
111111

112112
> [!IMPORTANT]
113113
> When running the agents and uploading the policy files, make sure they're uploaded in the correct order:
114114
>
115115
> 1. *TrustFrameworkBase.xml*
116+
> 1. *TrustFrameworkLocalization.xml*
116117
> 1. *TrustFrameworkExtensions.xml*
117118
> 1. *SignUpOrSignin.xml*
118119
> 1. *ProfileEdit.xml*

‎articles/active-directory-b2c/tutorial-create-user-flows.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ manager: celestedg
88
ms.service: active-directory
99
ms.workload: identity
1010
ms.topic: tutorial
11-
ms.date: 09/20/2021
11+
ms.date: 10/12/2021
1212
ms.author: mimart
1313
ms.subservice: B2C
1414
zone_pivot_groups: b2c-policy-type
@@ -251,6 +251,7 @@ Custom policies are a set of XML files you upload to your Azure AD B2C tenant to
251251
Each starter pack contains:
252252

253253
- **Base file** - Few modifications are required to the base. Example: *TrustFrameworkBase.xml*
254+
- **Localization file** - This file is where localization changes are made. Example: *TrustFrameworkLocalization.xml*
254255
- **Extension file** - This file is where most configuration changes are made. Example: *TrustFrameworkExtensions.xml*
255256
- **Relying party files** - Task-specific files called by your application. Examples: *SignUpOrSignin.xml*, *ProfileEdit.xml*, *PasswordReset.xml*
256257

@@ -285,10 +286,11 @@ Add the application IDs to the extensions file *TrustFrameworkExtensions.xml*.
285286
1. Select **Upload custom policy**.
286287
1. In this order, upload the policy files:
287288
1. *TrustFrameworkBase.xml*
288-
1. *TrustFrameworkExtensions.xml*
289-
1. *SignUpOrSignin.xml*
290-
1. *ProfileEdit.xml*
291-
1. *PasswordReset.xml*
289+
2. *TrustFrameworkLocalization.xml*
290+
3. *TrustFrameworkExtensions.xml*
291+
4. *SignUpOrSignin.xml*
292+
5. *ProfileEdit.xml*
293+
6. *PasswordReset.xml*
292294

293295
As you upload the files, Azure adds the prefix `B2C_1A_` to each.
294296

‎articles/active-directory-domain-services/join-ubuntu-linux-vm.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.service: active-directory
1010
ms.subservice: domain-services
1111
ms.workload: identity
1212
ms.topic: how-to
13-
ms.date: 07/13/2020
13+
ms.date: 10/11/2021
1414
ms.author: justinha
1515
ms.custom: fasttrack-edit
1616

@@ -31,7 +31,7 @@ To complete this tutorial, you need the following resources and privileges:
3131
* If needed, [create an Azure Active Directory tenant][create-azure-ad-tenant] or [associate an Azure subscription with your account][associate-azure-ad-tenant].
3232
* An Azure Active Directory Domain Services managed domain enabled and configured in your Azure AD tenant.
3333
* If needed, the first tutorial [creates and configures an Azure Active Directory Domain Services managed domain][create-azure-ad-ds-instance].
34-
* A user account that's a part of the managed domain.
34+
* A user account that's a part of the managed domain. Make sure the SAMAccountName attribute for the user is not autogenerated. If multiple user accounts in the Azure AD tenant have the same mailNickname attribute, the SAMAccountName attribute for each user is autogenerated. For more information, see [How objects and credentials are synchronized in an Azure Active Directory Domain Services managed domain](synchronization.md).
3535
* Unique Linux VM names that are a maximum of 15 characters to avoid truncated names that might cause conflicts in Active Directory.
3636

3737
## Create and connect to an Ubuntu Linux VM

‎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: 09/17/2021
4+
ms.date: 10/11/2021
55
ms.service: active-directory
66
ms.subservice: domain-services
77
author: justinha

‎articles/active-directory-domain-services/synchronization.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.service: active-directory
1010
ms.subservice: domain-services
1111
ms.workload: identity
1212
ms.topic: conceptual
13-
ms.date: 03/26/2021
13+
ms.date: 10/11/2021
1414
ms.author: justinha
1515

1616
---
@@ -72,7 +72,7 @@ The following table illustrates how specific attributes for user objects in Azur
7272
| mailNickname |SAMAccountName (may sometimes be autogenerated) |
7373
| manager |manager |
7474
| mobile |mobile |
75-
| objectid |msDS-AzureADObjectId |
75+
| objectid |msDS-aadObjectId |
7676
| onPremiseSecurityIdentifier |sidHistory |
7777
| passwordPolicies |userAccountControl (sets or clears the DONT_EXPIRE_PASSWORD bit) |
7878
| physicalDeliveryOfficeName |physicalDeliveryOfficeName |

‎articles/active-directory/authentication/howto-authentication-passwordless-deployment.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -297,7 +297,7 @@ Here are the sample test cases for passwordless authentication with security key
297297
| User can't perform combined registration.| Ensure [combined registration](concept-registration-mfa-sspr-combined.md) is enabled. |
298298
| User can't add a security key in their [security settings](https://aka.ms/mysecurityinfo).| Ensure that [security keys](howto-authentication-passwordless-security-key.md) are enabled. |
299299
| User can't add security key in Windows 10 sign-in options.| [Ensure that security keys for Windows sign in](concept-authentication-passwordless.md) are enabled |
300-
| **Error message**: We detected that this browser or OS doesn't support FIDO2 security keys.| Passwordless FIDO2 security devices can only be registered in supported browsers (Microsoft Edge, Firefox version 67) o Windows 10 version 1809 or higher. |
300+
| **Error message**: We detected that this browser or OS doesn't support FIDO2 security keys.| Passwordless FIDO2 security devices can only be registered in supported browsers (Microsoft Edge, Firefox version 67) on Windows 10 version 1809 or higher. |
301301
| **Error message**: Your company policy requires that you use a different method to sign in.| Ensure security keys are enabled in the tenant. |
302302
| User unable to manage my security key on Windows 10 version 1809| Version 1809 requires that you use the security key management software provided by the FIDO2 key vendor. Contact the vendor for support. |
303303
| I think my FIDO2 security key may be defective—how can I test it.| Navigate to [https://webauthntest.azurewebsites.net/](https://webauthntest.azurewebsites.net/), enter credentials for a test account, plug in the suspect security key, select the + button at the top right of the screen, select create, and go through the creation process. If this scenario fails, your device may be defective. |
@@ -382,4 +382,4 @@ Select the user row, and then select the **Authentication Details** tab to view
382382

383383
* [Learn how passwordless authentication works](concept-authentication-passwordless.md)
384384

385-
* [Deploy other identity features](../fundamentals/active-directory-deployment-plans.md)
385+
* [Deploy other identity features](../fundamentals/active-directory-deployment-plans.md)

0 commit comments

Comments
 (0)