Merge pull request #225375 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: huypub

articles/active-directory/develop/scenario-protected-web-api-app-configuration.md

@@ -70,7 +70,7 @@ You need to specify the `TenantId` only if you want to accept access tokens from
 {
   "AzureAd": {
     "Instance": "https://login.microsoftonline.com/",
-    "ClientId": "Enter_the_Application_(client)_ID_here"
+    "ClientId": "Enter_the_Application_(client)_ID_here",
     "TenantId": "common"
   },
   "Logging": {

articles/active-directory/governance/lifecycle-workflow-tasks.md

@@ -26,10 +26,6 @@ Lifecycle Workflow's built-in tasks each include an identifier, known as **taskD
 
 Common task parameters are the non-unique parameters contained in every task. When adding tasks to a new workflow, or a workflow template, you can customize and configure these parameters so that they match your requirements.
 
-
-> [!NOTE]
-> The user's employee hire date is used as the start time for the Temporary Access Pass. Please make sure that the TAP lifetime task setting and the [time portion of your user's hire date](how-to-lifecycle-workflow-sync-attributes.md#importance-of-time) are set appropriately so that the TAP is still valid when the user starts their first day.
-
 |Parameter  |Definition  |
 |---------|---------|
 |category     |  A  read-only string that identifies the category or categories of the task. Automatically determined when the taskDefinitionID is chosen.     |
@@ -123,21 +119,23 @@ For Microsoft Graph the parameters for the **Send onboarding reminder email** ta
 
 ### Generate Temporary Access Pass and send via email to user's manager
 
-When a compatible user joins your organization, Lifecycle Workflows allow you to automatically generate a Temporary Access Pass(TAP), and have it sent to the new user's manager.
+When a compatible user joins your organization, Lifecycle Workflows allow you to automatically generate a Temporary Access Pass (TAP), and have it sent to the new user's manager.
+
+> [!NOTE]
+> The user's employee hire date is used as the start time for the Temporary Access Pass. Please make sure that the TAP lifetime task setting and the [time portion of your user's hire date](how-to-lifecycle-workflow-sync-attributes.md#importance-of-time) are set appropriately so that the TAP is still valid when the user starts their first day. If the hire date at the time of workflow execution is already in the past, the current time is used as the start time.
 
 With this task in the Azure portal, you're able to give the task a name and description. You must also set:
 
-**Activation duration**- How long the password is active.
-**One time use**- If the password is one use only.
+- **Activation duration**- How long the passcode is active.
+- **One time use**- If the passcode can only be used once.
 :::image type="content" source="media/lifecycle-workflow-task/tap-task.png" alt-text="Screenshot of Workflows task: TAP task.":::
 
 
 The Azure AD prerequisites to run the **Generate Temporary Access Pass and send via email to user's manager** task are:
 
 - A populated manager attribute for the user.
 - A populated manager's mail attribute for the user.
-- An enabled TAP tenant policy. For more information, see [Enable the Temporary Access Pass policy](../authentication/howto-authentication-temporary-access-pass.md#enable-the-temporary-access-pass-policy)
- 
+- The TAP tenant policy must be enabled and the selected values for activation duration and one time use must be within the allowed range of the policy. For more information, see [Enable the Temporary Access Pass policy](../authentication/howto-authentication-temporary-access-pass.md#enable-the-temporary-access-pass-policy)
 
 > [!IMPORTANT]
 > A user having this task run for them in a workflow must also not have any other authentication methods, sign-ins, or AAD role assignments for this task to work for them.
@@ -175,10 +173,6 @@ For Microsoft Graph the parameters for the **Generate Temporary Access Pass and
 
 ```
 
-> [!NOTE]
-> The employee hire date is the same as the startDateTime used for the tapLifetimeInMinutes parameter.
-
-
 ### Add user to groups
 
 Allows users to be added to Microsoft 365 and cloud-only security groups. Mail-enabled, distribution, dynamic and privileged access groups are not supported. To control access to on-premises applications and resources, you need to enable group writeback. For more information, see [Azure AD Connect group writeback](../hybrid/how-to-connect-group-writeback-v2.md). 

articles/aks/learn/quick-windows-container-deploy-cli.md

@@ -27,6 +27,23 @@ This article assumes a basic understanding of Kubernetes concepts. For more info
 - If you have multiple Azure subscriptions, select the appropriate subscription ID in which the resources should be billed using the
 [az account](/cli/azure/account) command.
 
+- Verify _Microsoft.OperationsManagement_ and _Microsoft.OperationalInsights_ providers are registered on your subscription. These are Azure resource providers required to support Container insights. To check the registration status, run the following commands:
+
+  ```sh
+  az provider show -n Microsoft.OperationsManagement -o table
+  az provider show -n Microsoft.OperationalInsights -o table
+  ```
+
+  If they are not registered, register _Microsoft.OperationsManagement_ and _Microsoft.OperationalInsights_ using the following commands:
+  
+  ```sh
+  az provider register --namespace Microsoft.OperationsManagement
+  az provider register --namespace Microsoft.OperationalInsights
+  ```
+  
+  > [!NOTE]
+  > Run the commands with administrative privileges if you plan to run the commands in this quickstart locally instead of in Azure Cloud Shell.
+
 ### Limitations
 
 The following limitations apply when you create and manage AKS clusters that support multiple node pools:
@@ -408,5 +425,6 @@ To learn more about AKS, and walk through a complete code to deployment example,
 [aks-faq]: faq.md
 [az-extension-add]: /cli/azure/extension#az-extension-add
 [az-extension-update]: /cli/azure/extension#az-extension-update
+[azure-monitor-containers]: ../../azure-monitor/containers/container-insights-overview.md
 [windows-server-password]: /windows/security/threat-protection/security-policy-settings/password-must-meet-complexity-requirements#reference
 [win-faq-change-admin-creds]: ../windows-faq.md#how-do-i-change-the-administrator-password-for-windows-server-nodes-on-my-cluster

articles/azure-functions/storage-considerations.md

@@ -93,7 +93,7 @@ You can use the following strategies to avoid host ID collisions:
 
 You can explicitly set a specific host ID for your function app in the application settings by using the `AzureFunctionsWebHost__hostid` setting. For more information, see [AzureFunctionsWebHost__hostid](functions-app-settings.md#azurefunctionswebhost__hostid). 
 
-When the collision occurs between slots, you may need to mark this setting as a slot setting. To learn how to create app settings, see [Work with application settings](functions-how-to-use-azure-function-app-settings.md#settings).
+When the collision occurs between slots, you must set a specific host ID for each slot, including the production slot. You must also mark these settings as [deployment settings](functions-deployment-slots.md#create-a-deployment-setting) so they don't get swapped. To learn how to create app settings, see [Work with application settings](functions-how-to-use-azure-function-app-settings.md#settings).
 
 ## Azure Arc-enabled clusters
 

articles/cognitive-services/language-service/summarization/includes/quickstarts/python-sdk.md

@@ -14,7 +14,7 @@ ms.custom: ignite-fall-2021
 
 # [Conversation summarization](#tab/conversation-summarization)
 
-[Reference documentation](/python/api/overview/azure/ai-language-conversations-readme?preserve-view=true&view=azure-python-preview) | [Additional samples](https://github.com/Azure/azure-sdk-for-python/blob/azure-ai-language-conversations_1.1.0b2/sdk/cognitivelanguage/azure-ai-language-conversations/samples/README.md) | [Package (PyPi)](https://pypi.org/project/azure-ai-language-conversations/1.1.0b2/) | [Library source code](https://github.com/Azure/azure-sdk-for-python/tree/azure-ai-language-conversations_1.1.0b2/sdk/cognitivelanguage/azure-ai-language-conversations) 
+[Reference documentation](/python/api/overview/azure/ai-language-conversations-readme?preserve-view=true&view=azure-python-preview) | [Additional samples](https://github.com/Azure/azure-sdk-for-python/blob/azure-ai-language-conversations_1.1.0b3/sdk/cognitivelanguage/azure-ai-language-conversations/samples/README.md) | [Package (PyPi)](https://pypi.org/project/azure-ai-language-conversations/1.1.0b3/) | [Library source code](https://github.com/Azure/azure-sdk-for-python/tree/azure-ai-language-conversations_1.1.0b3/sdk/cognitivelanguage/azure-ai-language-conversations) 
 
 ---
 
@@ -49,7 +49,7 @@ pip install azure-ai-textanalytics==5.3.0b1
 # [Conversation summarization](#tab/conversation-summarization)
 
 ```console
-pip install azure-ai-language-conversations==1.1.0b2
+pip install azure-ai-language-conversations==1.1.0b3
 ```
 
 ---
@@ -155,84 +155,86 @@ with client:
                                 "text": "Hello, you’re chatting with Rene. How may I help you?",
                                 "id": "1",
                                 "role": "Agent",
-                                "participantId": "Agent_1"
+                                "participantId": "Agent_1",
                             },
                             {
                                 "text": "Hi, I tried to set up wifi connection for Smart Brew 300 coffee machine, but it didn’t work.",
                                 "id": "2",
                                 "role": "Customer",
-                                "participantId": "Customer_1"
+                                "participantId": "Customer_1",
                             },
                             {
                                 "text": "I’m sorry to hear that. Let’s see what we can do to fix this issue. Could you please try the following steps for me? First, could you push the wifi connection button, hold for 3 seconds, then let me know if the power light is slowly blinking on and off every second?",
                                 "id": "3",
                                 "role": "Agent",
-                                "participantId": "Agent_1"
+                                "participantId": "Agent_1",
                             },
                             {
                                 "text": "Yes, I pushed the wifi connection button, and now the power light is slowly blinking.",
                                 "id": "4",
                                 "role": "Customer",
-                                "participantId": "Customer_1"
+                                "participantId": "Customer_1",
                             },
                             {
                                 "text": "Great. Thank you! Now, please check in your Contoso Coffee app. Does it prompt to ask you to connect with the machine?",
                                 "id": "5",
                                 "role": "Agent",
-                                "participantId": "Agent_1"
+                                "participantId": "Agent_1",
                             },
                             {
                                 "text": "No. Nothing happened.",
                                 "id": "6",
                                 "role": "Customer",
-                                "participantId": "Customer_1"
+                                "participantId": "Customer_1",
                             },
                             {
                                 "text": "I’m very sorry to hear that. Let me see if there’s another way to fix the issue. Please hold on for a minute.",
                                 "id": "7",
                                 "role": "Agent",
-                                "participantId": "Agent_1"
-                            }
+                                "participantId": "Agent_1",
+                            },
                         ],
                         "modality": "text",
                         "id": "conversation1",
-                        "language": "en"
+                        "language": "en",
                     },
                 ]
             },
             "tasks": [
                 {
-                    "taskName": "analyze 1",
+                    "taskName": "Issue task",
+                    "kind": "ConversationalSummarizationTask",
+                    "parameters": {"summaryAspects": ["issue"]},
+                },
+                {
+                    "taskName": "Resolution task",
                     "kind": "ConversationalSummarizationTask",
-                    "parameters": {
-                        "summaryAspects": ["Issue, Resolution"]
-                    }
-                }
-            ]
+                    "parameters": {"summaryAspects": ["resolution"]},
+                },
+            ],
         }
     )
 
     # view result
     result = poller.result()
-    task_result = result["tasks"]["items"][0]
-    print("... view task status ...")
-    print("status: {}".format(task_result["status"]))
-    resolution_result = task_result["results"]
-    if resolution_result["errors"]:
-        print("... errors occured ...")
-        for error in resolution_result["errors"]:
-            print(error)
-    else:
-        conversation_result = resolution_result["conversations"][0]
-        if conversation_result["warnings"]:
-            print("... view warnings ...")
-            for warning in conversation_result["warnings"]:
-                print(warning)
+    task_results = result["tasks"]["items"]
+    for task in task_results:
+        print(f"\n{task['taskName']} status: {task['status']}")
+        task_result = task["results"]
+        if task_result["errors"]:
+            print("... errors occurred ...")
+            for error in task_result["errors"]:
+                print(error)
         else:
-            summaries = conversation_result["summaries"]
-            print("... view task result ...")
-            print("issue: {}".format(summaries[0]["text"]))
-            print("resolution: {}".format(summaries[1]["text"]))
+            conversation_result = task_result["conversations"][0]
+            if conversation_result["warnings"]:
+                print("... view warnings ...")
+                for warning in conversation_result["warnings"]:
+                    print(warning)
+            else:
+                summaries = conversation_result["summaries"]
+                for summary in summaries:
+                    print(f"{summary['aspect']}: {summary['text']}")
 
 ```
 
@@ -242,11 +244,11 @@ with client:
 ### Output
 
 ```console
-... view task status ...
-status: succeeded
-... view task result ...
-issue: Customer tried to set up wifi connection for Smart Brew 300 coffee machine, but it didn't work
-resolution: Asked customer to try the following steps | Asked customer for the power light | Helped customer to connect to the machine
+Issue task status: succeeded
+issue: Customer tried to set up wifi connection for Smart Brew 300 coffee machine but it didn't work. No error message.
+
+Resolution task status: succeeded
+resolution: Asked customer to check if the Contoso Coffee app prompts to connect with the machine. Customer ended the chat.
 ```
 
 ---

articles/deployment-environments/configure-catalog-item.md

@@ -19,7 +19,7 @@ In Azure Deployment Environments Preview, you can use a [catalog](concept-enviro
 A catalog item is combined of least two files:
 
 - An [Azure Resource Manager template (ARM template)](../azure-resource-manager/templates/overview.md) in JSON file format. For example, *azuredeploy.json*.
-- A manifest YAML file (*manifest.yml*).
+- A manifest YAML file (*manifest.yaml*).
 
 >[!NOTE]
 > Azure Deployment Environments Preview currently supports only ARM templates.

articles/deployment-environments/how-to-configure-use-cli.md

@@ -259,7 +259,7 @@ az devcenter admin project delete -g <resource-group-name> --name <project-name>
 **Create an environment**
 
 ```azurecli
-az devcenter dev environment create -g <resource-group-name> --dev-center-name <devcenter-name> \
+az devcenter dev environment create --dev-center-name <devcenter-name> \
     --project-name <project-name> -n <name> --environment-type <environment-type-name> \
     --catalog-item-name <catalog-item-name> ---catalog-name <catalog-name> \
     --parameters <deployment-parameters-json-string>