Merge pull request #253371 from MicrosoftDocs/main

09/29 PM Publishing

Author: v-alje

.docutune/config/docutune-azure-docs-pr.json

@@ -0,0 +1,40 @@
+{
+  "BaseConfiguration": "docutune-default.json",
+  "Docsets": [
+    {
+      "DocsetName": "azure-documents",
+      "BuildSourceFolder": "articles",
+      "BasePath": "/azure"
+  } ],
+  "MetadataDelimiter": "\"",
+  "Exclude": [
+    "licensing-service-plan-reference.md",
+    "policy-reference.md",
+    "security-controls-policy.md",
+    "articles/defender-for-cloud/alerts-reference.md",
+    "articles/defender-for-cloud/windows-admin-center-integration.md",
+    "articles/governance/",
+    "includes/policy/",
+    "includes/defender-for-cloud-alerts-schema-log-analytics-workspace.md",
+    "third-party-notices.md",
+    "*whats-new*",
+    "*release-notes*",
+    "*third-party-notices*",
+    "*change-log*",
+    "*changelog*",
+    "*reference-breaking-changes*",
+    "*version-history*",
+    "banner.md"
+  ],
+  "PreloadTOCFiles": [
+    "articles/cloud-services/toc.yml",
+    "articles/storage/blobs/TOC.yml",
+    "articles/storage/queues/TOC.yml"
+  ],
+  "TermFiles": [
+    "Dictionary-Onboard.ps1",
+    "Bundle-Standard.txt",
+    "Bundle-Cloud.txt"
+  ],
+  "ApplyPolicies": []
+}

.docutune/config/docutune-unattended.json

@@ -0,0 +1,34 @@
+{
+  "baseConfiguration": "docutune-unattended-default.json",
+  "onboarding": {
+    "maxInFlightPullRequests": 20,
+    "maxInFlightFiles": 200
+  },
+  "pullRequest": {
+    "title": "[BULK] [DocuTune-Remediation] - Scheduled execution to fix known issues in WAF",
+    "batchSize": 0,
+    "maxBatches": 100,
+    "body": "",
+    "newBranchNamePrefix": "",
+    "headRemote": "origin",
+    "draft": false,
+    "requestReview": true,
+    "signOff": false,
+    "properties": {},
+    "sleepInterval": 15
+  },
+  "types": [
+    {
+      "name": "Default",
+      "command": "Fix",
+      "configType": "full",
+      "stopAt": 9
+    },
+    {
+      "name": "FlagBrokenLinks",
+      "base": "Default",
+      "configType": "links-only",
+      "stopAt": 10
+    }
+  ]
+}

.openpublishing.redirection.azure-monitor.json

@@ -6319,6 +6319,21 @@
             "source_path_from_root": "/articles/azure-monitor/containers/container-insights-optout-openshift-v4.md",
             "redirect_url": "/azure/azure-monitor/containers/container-insights-optout",
             "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-monitor/app/opencensus-python-dependency.md",
+            "redirect_url": "/previous-versions/azure/azure-monitor/app/opencensus-python-dependency",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-monitor/app/opencensus-python-request.md",
+            "redirect_url": "/previous-versions/azure/azure-monitor/app/opencensus-python-request",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-monitor/app/opencensus-python.md",
+            "redirect_url": "/previous-versions/azure/azure-monitor/app/opencensus-python",
+            "redirect_document_id": false
         }
     ]
 }

articles/active-directory/authentication/howto-authentication-passwordless-faqs.md

@@ -248,6 +248,9 @@ Microsoft Entra ID combines the encrypted client key and message buffer into the
 | tgt_key_type       | int    | The on-premises AD DS key type used for both the client key and the Kerberos session key included in the KERB_MESSAGE_BUFFER. |
 | tgt_message_buffer | string | Base64 encoded KERB_MESSAGE_BUFFER. |
 
+### Do users need to be a member of the Domain Users Active Directory group?
+Yes. A user must be in the Domain Users group to be able to sign-in using Azure AD Kerberos.
+
 ## Next steps
 
 To get started with FIDO2 security keys and hybrid access to on-premises resources, see the following articles:

articles/active-directory/authentication/howto-authentication-sms-signin.md

@@ -66,6 +66,8 @@ First, let's enable SMS-based authentication for your Microsoft Entra tenant.
 
 
 1. Click **Enable** and select **Target users**. You can choose to enable SMS-based authentication for *All users* or *Select users* and groups. 
+   > [!NOTE]
+   > To configure SMS-based authentication for first-factor (that is, to allow users to sign in with this method), check the **Use for sign-in** checkbox. Leaving this unchecked makes SMS-based authentication available for multifactor authentication and Self-Service Password Reset only.
 
     ![Enable SMS authentication in the authentication method policy window](./media/howto-authentication-sms-signin/enable-sms-authentication-method.png)
 

articles/active-directory/devices/howto-vm-sign-in-azure-ad-linux.md

@@ -158,7 +158,7 @@ az group create --name AzureADLinuxVM --location southcentralus
 az vm create \
     --resource-group AzureADLinuxVM \
     --name myVM \	
-    --image UbuntuLTS \
+    --image Ubuntu2204 \
     --assign-identity \
     --admin-username azureuser \
     --generate-ssh-keys

articles/active-directory/fundamentals/how-to-rename-azure-ad.md

@@ -6,14 +6,14 @@ author: CelesteDG
 manager: CelesteDG
 ms.service: active-directory
 ms.subservice: fundamentals
-ms.custom: docutune-disable
 ms.topic: how-to
 ms.date: 09/27/2023
 ms.author: celested
 ms.reviewer: nicholepet
 
 # Customer intent: As a content creator, employee of an organization with internal documentation for IT or identity security admins, developer of Azure AD-enabled apps, ISV, or Microsoft partner, I want to learn how to correctly update our documentation or content to use the new name for Azure AD.
 ---
+
 # How to: Rename Azure AD
 
 Azure Active Directory (Azure AD) is being renamed to Microsoft Entra ID to better communicate the multicloud, multiplatform functionality of the product and unify the naming of the Microsoft Entra product family.
@@ -22,7 +22,7 @@ This article provides best practices and support for customers and organizations
 
 ## Prerequisites
 
-Before changing instances of Azure AD in your documentation or content, familiarize yourself with the guidance in [New name for Azure AD](new-name.md) to:
+Before changing instances of Azure AD in your documentation or content, familiarize yourself with the guidance in [New name for Azure AD](./new-name.md) to:
 
 - Understand the product name and why we made the change
 - Download the new product icon
@@ -69,27 +69,27 @@ Update your organization's content and experiences using the relevant tools.
 Use the following criteria to determine what change(s) you need to make to instances of `Azure Active Directory (Azure AD)`, `Azure Active Directory`, `Azure AD`, `AAD`.
 
 1. If the text string is found in the naming dictionary of previous terms, change it to the new term.
-1. If a punctuation mark follows "Azure Active Directory (Azure AD), Azure Active Directory, Azure AD, AAD," replace with 'Microsoft Entra ID' because that's the product name.
-1. If `Azure Active Directory (Azure AD)`, `Azure Active Directory`, `Azure AD`, `AAD` is followed by `for`, `Premium`, `Plan`, `P1`, or `P2`, replace with `Microsoft Entra ID` because it refers to a SKU name or Service Plan.
+1. If a punctuation mark follows `Azure Active Directory (Azure AD)`, `Azure Active Directory`, `Azure AD`, or `AAD`, replace with `Microsoft Entra ID` because that's the product name.
+1. If `Azure Active Directory (Azure AD)`, `Azure Active Directory`, `Azure AD`, or `AAD` is followed by `for`, `Premium`, `Plan`, `P1`, or `P2`, replace with `Microsoft Entra ID` because it refers to a SKU name or Service Plan.
 1. If an article (`a`, `an`, `the`) or possessive (`your`, `your organization's`) precedes (`Azure Active Directory (Azure AD)`, `Azure Active Directory`, `Azure AD`, `AAD`), then replace with `Microsoft Entra` because it's a feature name. For example:
    1. "an Azure AD tenant" becomes "a Microsoft Entra tenant"
    1. "your organization's Azure AD tenant" becomes "your Microsoft Entra tenant"
 
-1. If `Azure Active Directory (Azure AD)`, `Azure Active Directory`, `Azure AD`, `AAD` is followed by an adjective or noun not in the previous steps, then replace with `Microsoft Entra` because it's a feature name. For example,"Azure AD Conditional Access" becomes "Microsoft Entra Conditional Access," while "Azure AD tenant" becomes "Microsoft Entra tenant."
-1. Otherwise, replace `Azure Active Directory (Azure AD)`, `Azure Active Directory`, `Azure AD`, `AAD` with `Microsoft Entra ID`
+1. If `Azure Active Directory (Azure AD)`, `Azure Active Directory`, `Azure AD`, or `AAD` is followed by an adjective or noun not in the previous steps, then replace with `Microsoft Entra` because it's a feature name. For example, `Azure AD Conditional Access` becomes `Microsoft Entra Conditional Access`, while `Azure AD tenant` becomes `Microsoft Entra tenant`.
+1. Otherwise, replace `Azure Active Directory (Azure AD)`, `Azure Active Directory`, `Azure AD`, or `AAD` with `Microsoft Entra ID`.
 
 See the section [Glossary of updated terminology](new-name.md#glossary-of-updated-terminology) to further refine your custom logic.
 
 ### Update graphics and icons
 
 1. Replace the Azure AD icon with the Microsoft Entra ID icon.
-1. Replace titles or text containing `Azure Active Directory (Azure AD)`, `Azure Active Directory`, `Azure AD`, `AAD` with `Microsoft Entra ID`.
+1. Replace titles or text containing `Azure Active Directory (Azure AD)`, `Azure Active Directory`, `Azure AD`, or `AAD` with `Microsoft Entra ID`.
 
 ## Sample PowerShell script
 
 You can use following PowerShell script as a baseline to rename Azure AD references in your documentation or content. This code sample:
 
-- Scans .resx files within a specified folder and all nested folders.
+- Scans `.resx` files within a specified folder and all nested folders.
 - Edits files by replacing any references to `Azure Active Directory (Azure AD)`, `Azure Active Directory`, `Azure AD`, `AAD` with the correct terminology according to [New name for Azure AD](new-name.md).
 
 Edit the baseline script according to your needs and the scope of files you need to update. You may need to account for edge cases and modify the script according to how you've defined the messages in your source files. The script is not fully automated. If you use the script as-is, you must review the outputs and may need to make additional adjustments to follow the guidance in [New name for Azure AD](new-name.md).
@@ -283,12 +283,12 @@ $postTransforms = @(
     @{ Key = ' an ME-ID'; Value = ' a ME-ID' }
     @{ Key = '>An ME-ID'; Value = '>A ME-ID' }
     @{ Key = 'Microsoft Entra ID administration portal'; Value = 'Microsoft Entra administration portal' }
-    @{ Key = 'Microsoft Entra IDvanced Threat'; Value = 'Azure Advanced Threat' }
+    @{ Key = 'Microsoft Entra ID Advanced Threat'; Value = 'Azure Advanced Threat' }
     @{ Key = 'Entra ID hybrid join'; Value = 'Entra hybrid join' }
     @{ Key = 'Microsoft Entra ID join'; Value = 'Microsoft Entra join' }
     @{ Key = 'ME-ID join'; Value = 'Microsoft Entra join' }
     @{ Key = 'Microsoft Entra ID service principal'; Value = 'Microsoft Entra service principal' }
-    @{ Key = 'DownloMicrosoft Entra Connector'; Value = 'Download connector' }
+    @{ Key = 'Download Microsoft Entra Connector'; Value = 'Download connector' }
     @{ Key = 'Microsoft Microsoft'; Value = 'Microsoft' }
 )
 
@@ -365,6 +365,8 @@ To help your customers with the transition, it's helpful to add a note: "Azure A
 
 ## Next steps
 
-- [Stay up-to-date with what's new in Azure AD/Microsoft Entra ID](whats-new.md)
+- [Stay up-to-date with what's new in Microsoft Entra ID (formerly Azure AD)](./whats-new.md)
 - [Get started using Microsoft Entra ID at the Microsoft Entra admin center](https://entra.microsoft.com/)
-- [Learn more about Microsoft Entra with content from Microsoft Learn](/entra)
+- [Learn more about Microsoft Entra ID with content from Microsoft Learn](/entra)
+
+<!-- docutune:ignore "Azure Active Directory" "Azure AD" "AAD" -->

articles/active-directory/fundamentals/new-name.md

@@ -6,7 +6,7 @@ author: CelesteDG
 manager: CelesteDG
 ms.service: active-directory
 ms.subservice: fundamentals
-ms.custom: has-azure-ad-ps-ref, docutune-disable
+ms.custom: has-azure-ad-ps-ref
 ms.topic: overview
 ms.date: 09/27/2023
 ms.author: celested
@@ -17,7 +17,7 @@ ms.reviewer: nicholepet
 
 # New name for Azure Active Directory
 
-To communicate the multicloud, multiplatform functionality of the products, alleviate confusion with Windows Server Active Directory, and unify the [Microsoft Entra](/entra) product family, the new name for Azure Active Directory (Azure AD) is Microsoft Entra ID.  
+To communicate the multicloud, multiplatform functionality of the products, alleviate confusion with Windows Server Active Directory, and unify the [Microsoft Entra](/entra) product family, the new name for Azure Active Directory (Azure AD) is Microsoft Entra ID.
 
 ## No interruptions to usage or service
 
@@ -95,7 +95,7 @@ The Microsoft Entra ID name more accurately represents the multicloud and multip
 
 ### What is Microsoft Entra?
 
-Microsoft Entra helps you protect all identities and secure network access everywhere. The expanded product family includes:
+The Microsoft Entra product family helps you protect all identities and secure network access everywhere. The expanded product family includes:
 
 | Identity and access management | New identity categories | Network access |
 |---------|---------|---------|
@@ -167,7 +167,7 @@ There are no changes to the identity features and functionality available in Mic
 
 ### What's changing for Microsoft 365 E5?
 
-In addition to the capabilities they already have, Microsoft 365 E5 customers also get access to new identity protection capabilities like token protection, Conditional Access based on GPS-based location and step-up authentication for the most sensitive actions. Microsoft 365 E5 includes Microsoft Entra P2, currently known as Azure AD Premium P2.
+In addition to the capabilities they already have, Microsoft 365 E5 customers also get access to new identity protection capabilities like token protection, Conditional Access based on GPS-based location and step-up authentication for the most sensitive actions. Microsoft 365 E5 includes Microsoft Entra ID P2, currently known as Azure AD Premium P2.
 
 ### What's changing for identity developer and devops experience?
 
@@ -299,6 +299,8 @@ Only official product names are capitalized, plus Conditional Access and My * ap
 ## Next steps
 
 - [How to: Rename Azure AD](how-to-rename-azure-ad.md)
-- [Stay up-to-date with what's new in Azure AD/Microsoft Entra ID](whats-new.md)
+- [Stay up-to-date with what's new in Microsoft Entra ID (formerly Azure AD)](./whats-new.md)
 - [Get started using Microsoft Entra ID at the Microsoft Entra admin center](https://entra.microsoft.com/)
-- [Learn more about Microsoft Entra with content from Microsoft Learn](/entra)
+- [Learn more about the Microsoft Entra family with content from Microsoft Learn](/entra)
+
+<!-- docutune:ignore "Azure Active Directory" "Azure AD" "AAD" "Entra ID" "Cloud Knox" "Identity Governance" -->

articles/active-directory/governance/how-to-lifecycle-workflow-sync-attributes.md

@@ -31,10 +31,10 @@ The following table shows the scheduling (trigger) relevant attributes and the m
 > [!NOTE]
 > Manually setting the employeeLeaveDateTime for cloud-only users requires special permissions. For more information, see: [Configure the employeeLeaveDateTime property for a user](/graph/tutorial-lifecycle-workflows-set-employeeleavedatetime)
 
-This document explains how to set up synchronization from on-premises Microsoft Entra Connect cloud sync and Microsoft Entra Connect for the required attributes.
+This document explains how to set up synchronization from on-premises Microsoft Entra Connect cloud sync or Microsoft Entra Connect for the required attributes.
 
 >[!NOTE]
-> There's no corresponding EmployeeHireDate or EmployeeLeaveDateTime attribute in Active Directory. If you're importing from on-premises AD, you'll need to identify an attribute in AD that can be used. This attribute must be a string.
+> There's no corresponding EmployeeHireDate or EmployeeLeaveDateTime attribute in Active Directory. If you're synchronizing from on-premises AD, you'll need to identify an attribute in AD that can be used. This attribute must be a string.
 
 
 ## Understanding EmployeeHireDate and EmployeeLeaveDateTime formatting
@@ -173,7 +173,7 @@ To update this mapping, you'd do the following:
 1.  Add your source attribute(s) created as Type String, and select on the CheckBox for required.
     :::image type="content" source="media/how-to-lifecycle-workflow-sync-attributes/edit-attribute-list.png" alt-text="Screenshot of source api list.":::
     > [!NOTE]
-    > The number, and name, of source attributes added will depend on which attributes you are syncing.
+    > The number, and name, of source attributes added will depend on which attributes you are syncing from Active Directory.
 1.  Select Save. 
 
 1. From there you must map the HRM attributes to the added Active Directory attributes. To do this, Add New Mapping using an Expression. 

articles/active-directory/manage-apps/admin-consent-workflow-overview.md

@@ -32,7 +32,7 @@ As an admin, the following options exist for you to determine how users consent
 - Disable user consent. For example, a high school may want to turn off user consent so that the school IT administration has full control over all the applications that are used in their tenant. 
 - Allow users to consent to the required permissions. It's NOT recommended to keep user consent open if you have sensitive data in your tenant. 
 - If you still want to retain admin-only consent for certain permissions but want to assist your end-users in onboarding their application, you can use the admin consent workflow to evaluate and respond to admin consent requests. This way, you can have a queue of all the requests for admin consent for your tenant and can track and respond to them directly through the Microsoft Entra admin center. 
-To learn how to configure the admin consent workflow, see [configure-admin-consent-workflow.md](configure-admin-consent-workflow.md).
+To learn how to configure the admin consent workflow, see [Configure the admin consent workflow](configure-admin-consent-workflow.md).
 
 ## How the admin consent workflow works