Merge pull request #261024 from MicrosoftDocs/repo_sync_working_branch

Taojunshen · web-flow · commit e8b711c86e74 · 2023-12-13T06:45:15.000+08:00
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
diff --git a/articles/ai-services/computer-vision/how-to/video-retrieval.md b/articles/ai-services/computer-vision/how-to/video-retrieval.md
@@ -207,7 +207,7 @@ Connection: close
 After you add video files to the index, the ingestion process starts. It might take some time depending on the size and number of files. To ensure the ingestion is complete before performing searches, you can use the **[Get Ingestion](../reference-video-search.md)** API to check the status. Wait for this call to return `"state" = "Completed"` before proceeding to the next step. 
 
 ```bash
-curl.exe -v _X GET "https://<YOUR_ENDPOINT_URL>/computervision/retrieval/indexes/my-video-index/ingestions?api-version=2023-05-01-preview&$top=20" -H "ocp-apim-subscription-key: <YOUR_SUBSCRIPTION_KEY>"
+curl.exe -v -X GET "https://<YOUR_ENDPOINT_URL>/computervision/retrieval/indexes/my-video-index/ingestions?api-version=2023-05-01-preview&$top=20" -H "ocp-apim-subscription-key: <YOUR_SUBSCRIPTION_KEY>"
 ```
 
 **Response:**
@@ -242,7 +242,7 @@ After you add video files to the index, you can search for specific videos using
 To perform a search using the "vision" feature, use the [Search By Text](../reference-video-search.md) API with the `vision` filter, specifying the query text and any other desired filters.
 
 ```bash
-POST -v -X "https://<YOUR_ENDPOINT_URL>/computervision/retrieval/indexes/my-video-index:queryByText?api-version=2023-05-01-preview" -H "Ocp-Apim-Subscription-Key: <YOUR_SUBSCRIPTION_KEY>" -H "Content-Type: application/json" --data-ascii "
+curl.exe -v -X POST "https://<YOUR_ENDPOINT_URL>/computervision/retrieval/indexes/my-video-index:queryByText?api-version=2023-05-01-preview" -H "Ocp-Apim-Subscription-Key: <YOUR_SUBSCRIPTION_KEY>" -H "Content-Type: application/json" --data-ascii "
 {
   'queryText': 'a man with black hoodie',
   'filters': {
diff --git a/articles/ai-services/document-intelligence/media/quickstarts/cors-updated-image.png b/articles/ai-services/document-intelligence/media/quickstarts/cors-updated-image.png
diff --git a/articles/ai-services/document-intelligence/quickstarts/try-document-intelligence-studio.md b/articles/ai-services/document-intelligence/quickstarts/try-document-intelligence-studio.md
@@ -110,7 +110,7 @@ For custom projects, the following role assignments are required for different s
 
 1. Start by creating a new CORS entry in the Blob service.
 
-1. Set the **Allowed origins** to `https://formrecognizer.appliedai.azure.com`.
+1. Set the **Allowed origins** to `https://documentintelligence.ai.azure.com`.
 
    :::image type="content" source="../media/quickstarts/cors-updated-image.png" alt-text="Screenshot that shows CORS configuration for a storage account.":::
 
diff --git a/articles/ai-services/language-service/language-studio.md b/articles/ai-services/language-service/language-studio.md
@@ -66,7 +66,8 @@ When you're ready to use Language Studio features on your own text data, you wil
 
 If you're sending conversational text to supported features in Language Studio, be aware of the following input requirements: 
 * The text you send must be a conversational dialog between two or more participants.
-* Each line must start with the name of the participant, followed by a `:`, and followed by what they say.
+* Except issue/resolution summarization, each line must start with the name of the participant, followed by a `:`, and followed by what they say.
+* To use issue and resolution aspects in conversation summarization, each line must start with the role of the participant between "Customer" and "Agent" spelled in English, followed by a ':' before what they say in any supported languages. Names of participants, followed by the role, are optional. 
 * Each participant must be on a new line. If multiple participants' utterances are on the same line, it will be processed as one line of the conversation.
 
 See the following example for how you should structure conversational text you want to send.
diff --git a/articles/ai-services/language-service/question-answering/concepts/confidence-score.md b/articles/ai-services/language-service/question-answering/concepts/confidence-score.md
@@ -23,7 +23,7 @@ The following table indicates typical confidence associated for a given score.
 |Score Value|Score Meaning|Example Query|
 |--|--|--|
 |0.90 - 1.00|A near exact match of user query and a KB question|
-|> 70|High confidence - typically a good answer that completely answers the user's query|
+|> 0.70|High confidence - typically a good answer that completely answers the user's query|
 |0.50 - 0.70|Medium confidence - typically a fairly good answer that should answer the main intent of the user query|
 |0.30 - 0.50|Low confidence - typically a related answer, that partially answers the user's intent|
 |< 0.30|Very low confidence - typically does not answer the user's query, but has some matching words or phrases |
diff --git a/articles/ai-services/language-service/summarization/overview.md b/articles/ai-services/language-service/summarization/overview.md
@@ -77,8 +77,10 @@ This documentation contains the following article types:
 Conversation summarization supports the following features:
 
 * **Issue/resolution summarization**: A call center specific feature that gives a summary of issues and resolutions in conversations between customer-service agents and your customers.
-* **Chapter title summarization**: Gives suggested chapter titles of the input conversation.
-* **Narrative summarization**: Gives call notes, meeting notes or chat summaries of the input conversation.
+* **Chapter title summarization**: Segments a conversation into chapters based on the topics discussed in the conversation, and gives suggested chapter titles of the input conversation.
+* **Recap**: Summarizes a conversation into a brief paragraph.
+* **Narrative summarization**: Generates detail call notes, meeting notes or chat summaries of the input conversation.
+* **Follow-up tasks**: Gives a list of follow-up tasks discussed in the input conversation.
 
 ## When to use issue and resolution summarization
 
diff --git a/articles/ai-services/language-service/text-analytics-for-health/includes/features.md b/articles/ai-services/language-service/text-analytics-for-health/includes/features.md
@@ -38,6 +38,7 @@ Entity linking is used to disambiguate the extracted entities by associating the
 * Certainty
 * Conditionality
 * Association
+* Temporality
 
 > [!div class="mx-imgBorder"]
 > ![Text Analytics for health negation](../media/call-api/assertions.png)
diff --git a/articles/ai-services/language-service/text-analytics-for-health/language-support.md b/articles/ai-services/language-service/text-analytics-for-health/language-support.md
@@ -18,7 +18,7 @@ Use this article to learn which natural languages are supported by Text Analytic
 
 ## Hosted API Service
 
-The hosted API service supports the English, Spanish, French, German, Italian, Portuguese and Hebrew languages.
+The hosted API service supports the English, Spanish, French, German, Italian, and Portuguese languages.
 
 When structuring the API request, the relevant language tags must be added for these languages: 
 
@@ -29,7 +29,6 @@ French  - “fr”
 German – “de”
 Italian – “it”
 Portuguese – “pt”
-Hebrew – “he”
 ```
 ```json
 json
@@ -112,17 +111,6 @@ json
     ]
 }
 ```
-## Details of the supported container tags:
-
-
-| Language Code       |  Featured Tag | Specific Tag |
-|:--------------------|:-------------------:|:------------------:|
-| `en`                  |      latest         |   3.0.59413252-onprem-amd64    | 
-| `en`, `es`, `it`, `fr`, `de`, `pt`   |      latin         |   3.0.60903415-latin-onprem-amd64    | 
-| `he`                  |      semitic         |   3.0.60903415-semitic-onprem-amd64   | 
-
-
-
 
 
 
diff --git a/articles/ai-services/language-service/text-analytics-for-health/overview.md b/articles/ai-services/language-service/text-analytics-for-health/overview.md
@@ -29,7 +29,7 @@ Text Analytics for health performs four key functions which are named entity rec
 
 [!INCLUDE [Text Analytics for health](includes/features.md)]
 
-Text Analytics for health can receive unstructured text in English as part of its generally available offering. Additional languages such as German, French, Italian, Spanish, Portuguese, and Hebrew are currently supported in preview.
+Text Analytics for health can receive unstructured text in English, German, French, Italian, Spanish, Portuguese, and Hebrew.
 
 Additionally, Text Analytics for health can return the processed output using the Fast Healthcare Interoperability Resources (FHIR) structure which enables the service's integration with other electronic health systems.  
 
diff --git a/articles/ai-services/openai/toc.yml b/articles/ai-services/openai/toc.yml
@@ -45,7 +45,7 @@ items:
       href: ./concepts/fine-tuning-considerations.md
     - name: Red teaming large language models (LLMs)
       href: ./concepts/red-teaming.md
-    - name: Image provenance
+    - name: Content credentials
       href: ./concepts/content-credentials.md
     - name: Intro to prompt engineering
       href: ./concepts/prompt-engineering.md
diff --git a/articles/ai-services/speech-service/migrate-v3-0-to-v3-1.md b/articles/ai-services/speech-service/migrate-v3-0-to-v3-1.md
@@ -39,8 +39,8 @@ For more details, see [Operation IDs](#operation-ids) later in this guide.
 > Don't use Speech to text REST API v3.0 to retrieve a transcription created via Speech to text REST API v3.1. You'll see an error message such as the following: "The API version cannot be used to access this transcription. Please use API version v3.1 or higher."
 
 In the [Transcriptions_Create](https://eastus.dev.cognitive.microsoft.com/docs/services/speech-to-text-api-v3-1/operations/Transcriptions_Create) operation the following three properties are added:
-- The `displayFormWordLevelTimestampsEnabled` property can be used to enable the reporting of word-level timestamps on the display form of the transcription results. The results are returned in the `displayWords` property of the transcription file. 
-- The `diarization` property can be used to specify hints for the minimum and maximum number of speaker labels to generate when performing optional diarization (speaker separation). With this feature, the service is now able to generate speaker labels for more than two speakers. To use this property you must also set the `diarizationEnabled` property to `true`. 
+- The `displayFormWordLevelTimestampsEnabled` property can be used to enable the reporting of word-level timestamps on the display form of the transcription results. The results are returned in the `displayWords` property of the transcription file.
+- The `diarization` property can be used to specify hints for the minimum and maximum number of speaker labels to generate when performing optional diarization (speaker separation). With this feature, the service is now able to generate speaker labels for more than two speakers. To use this property you must also set the `diarizationEnabled` property to `true`. With the v3.1 API we have increased the number of speakers that can be identified through diarization from the 2 speakers supported by the v3.0 API. It is recommended to keep the number of speakers under 30 for better performance.
 - The `languageIdentification` property can be used specify settings for language identification on the input prior to transcription. Up to 10 candidate locales are supported for language identification. The returned transcription will include a new `locale` property for the recognized language or the locale that you provided. 
 
 The `filter` property is added to the [Transcriptions_List](https://eastus.dev.cognitive.microsoft.com/docs/services/speech-to-text-api-v3-1/operations/Transcriptions_List), [Transcriptions_ListFiles](https://eastus.dev.cognitive.microsoft.com/docs/services/speech-to-text-api-v3-1/operations/Transcriptions_ListFiles), and [Projects_ListTranscriptions](https://eastus.dev.cognitive.microsoft.com/docs/services/speech-to-text-api-v3-1/operations/Projects_ListTranscriptions) operations. The `filter` expression can be used to select a subset of the available resources. You can filter by `displayName`, `description`, `createdDateTime`, `lastActionDateTime`, `status`, and `locale`. For example: `filter=createdDateTime gt 2022-02-01T11:00:00Z`
diff --git a/articles/aks/azure-ad-rbac.md b/articles/aks/azure-ad-rbac.md
@@ -73,7 +73,7 @@ In production environments, you can use existing users and groups within a Micro
 2. Create the first example group in Microsoft Entra ID for the application developers using the [`az ad group create`][az-ad-group-create] command. The following example creates a group named *appdev*:
 
     ```azurecli-interactive
-    APPDEV_ID=$(az ad group create --display-name appdev --mail-nickname appdev --query Id -o tsv)
+    APPDEV_ID=$(az ad group create --display-name appdev --mail-nickname appdev --query id -o tsv)
     ```
 
 3. Create an Azure role assignment for the *appdev* group using the [`az role assignment create`][az-role-assignment-create] command. This assignment lets any member of the group use `kubectl` to interact with an AKS cluster by granting them the *Azure Kubernetes Service Cluster User* Role.
@@ -91,7 +91,7 @@ In production environments, you can use existing users and groups within a Micro
 4. Create a second example group for SREs named *opssre*.
 
     ```azurecli-interactive
-    OPSSRE_ID=$(az ad group create --display-name opssre --mail-nickname opssre --query objectId -o tsv)
+    OPSSRE_ID=$(az ad group create --display-name opssre --mail-nickname opssre --query id -o tsv)
     ```
 
 5. Create an Azure role assignment to grant members of the group the *Azure Kubernetes Service Cluster User* Role.
diff --git a/articles/azure-functions/functions-how-to-custom-container.md b/articles/azure-functions/functions-how-to-custom-container.md
@@ -194,6 +194,9 @@ Azure Functions lets you work with application settings for containerized functi
 :::zone pivot="azure-functions"
 ## Enable continuous deployment to Azure
 
+> [!IMPORTANT]
+> Webhook-based deployment isn't currently supported when running your container in an [Elastic Premium plan](functions-premium-plan.md). If you need to use the continuous deployment method described in this section, instead deploy your container in an [App Service plan](dedicated-plan.md). When running in an Elastic Premium plan, you need to manually restart your app whenever you make updates to your container in the repository.
+
 You can enable Azure Functions to automatically update your deployment of an image whenever you update the image in the registry.
 
 1. Use the following command to enable continuous deployment and to get the webhook URL:
diff --git a/articles/azure-monitor/agents/use-azure-monitor-agent-troubleshooter.md b/articles/azure-monitor/agents/use-azure-monitor-agent-troubleshooter.md
@@ -38,7 +38,7 @@ The Azure Monitor Agent isn't a service that runs in the context of an Azure Res
 ## Windows Troubleshooter
 ### Run Windows Troubleshooter
 1. Log in to the machine to be diagnosed as Administator
-2. Run script in power shell
+2. Run script in PowerShell
    
    ```PowerShell
    $currentVersion = ((Get-ChildItem -Path "Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Azure\HandlerState\" `
diff --git a/articles/sentinel/data-connectors/sonicwall-firewall.md b/articles/sentinel/data-connectors/sonicwall-firewall.md
@@ -75,7 +75,7 @@ Install the Microsoft Monitoring Agent on your Linux machine and configure the m
 
    Run the following command to install and apply the CEF collector:
 
-  `sudo wget -O cef_installer.py https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/DataConnectors/CEF/cef_installer.py&&sudo python cef_installer.py {0} {1}`
+  `sudo wget -O cef_installer.py https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/DataConnectors/CEF/cef_installer.py&&sudo python cef_installer.py [Workspace ID] [Workspace Primary Key]`
 
 2. Forward SonicWall Firewall Common Event Format (CEF) logs to Syslog agent
 
@@ -99,7 +99,7 @@ If the logs are not received, run the following connectivity validation script:
 
    Run the following command to validate your connectivity:
 
-   `sudo wget -O cef_installer.py https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/DataConnectors/CEF/cef_troubleshoot.py&&sudo python cef_troubleshoot.py  {0}`
+   `sudo wget -O cef_troubleshoot.py https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/DataConnectors/CEF/cef_troubleshoot.py&&sudo python cef_troubleshoot.py [Workspace ID]`
 
 4. Secure your machine 
 
diff --git a/articles/storage/blobs/object-replication-overview.md b/articles/storage/blobs/object-replication-overview.md
@@ -6,8 +6,8 @@ author: normesta
 
 ms.service: azure-blob-storage
 ms.topic: conceptual
-ms.date: 05/04/2023
-ms.author: normesta
+ms.date: 12/08/2023
+ms.author: nachakra
 ms.custom: engagement-fy23
 ---
 
@@ -178,13 +178,13 @@ The following table summarizes which values to use for the **policyId** and **ru
 
 A Microsoft Entra tenant is a dedicated instance of Microsoft Entra ID that represents an organization for identity and access management. Each Azure subscription has a trust relationship with a single Microsoft Entra tenant. All resources in a subscription, including storage accounts, are associated with the same Microsoft Entra tenant. For more information, see [What is Microsoft Entra ID?](../../active-directory/fundamentals/active-directory-whatis.md)
 
-By default, cross-tenant replication is disabled in the Azure portal. If your security policies require that you restrict object replication to storage accounts that reside within the same tenant only, you can disallow replication across tenants by setting a security property, the **AllowCrossTenantReplication** property (preview). When you disallow cross-tenant object replication for a storage account, then for any object replication policy that is configured with that storage account as the source or destination account, Azure Storage requires that both the source and destination accounts reside within the same Microsoft Entra tenant. For more information about disallowing cross-tenant object replication, see [Prevent object replication across Microsoft Entra tenants](object-replication-prevent-cross-tenant-policies.md).
+By default, cross-tenant replication is disabled for new accounts created starting Dec 15, 2023. If your security policies require that you restrict object replication to storage accounts that reside within the same tenant only, you can disallow replication across tenants by setting a security property, the **AllowCrossTenantReplication** property (preview). When you disallow cross-tenant object replication for a storage account, then for any object replication policy that is configured with that storage account as the source or destination account, Azure Storage requires that both the source and destination accounts reside within the same Microsoft Entra tenant. For more information about disallowing cross-tenant object replication, see [Prevent object replication across Microsoft Entra tenants](object-replication-prevent-cross-tenant-policies.md).
 
 To disallow cross-tenant object replication for a storage account, set the **AllowCrossTenantReplication** property to *false*. If the storage account doesn't currently participate in any cross-tenant object replication policies, then setting the **AllowCrossTenantReplication** property to *false* prevents future configuration of cross-tenant object replication policies with this storage account as the source or destination.
 
 If the storage account currently participates in one or more cross-tenant object replication policies, then setting the **AllowCrossTenantReplication** property to *false* isn't permitted. You must delete the existing cross-tenant policies before you can disallow cross-tenant replication.
 
-By default, the **AllowCrossTenantReplication** property isn't set for a storage account, and its value is *null*, which is equivalent to *false*. When the value of the **AllowCrossTenantReplication** property for a storage account is *null* or *true*, then authorized users can configure cross-tenant object replication policies with this account as the source or destination. For more information about how to configure cross-tenant policies, see [Configure object replication for block blobs](object-replication-configure.md).
+By default, the **AllowCrossTenantReplication** property is set to false for a storage account created starting Dec 15, 2023. For storage accounts created prior to Dec 15, 2023, when the value of the **AllowCrossTenantReplication** property for a storage account is *null* or *true*, then authorized users can configure cross-tenant object replication policies with this account as the source or destination. For more information about how to configure cross-tenant policies, see [Configure object replication for block blobs](object-replication-configure.md).
 
 You can use Azure Policy to audit a set of storage accounts to ensure that the **AllowCrossTenantReplication** property is set to prevent cross-tenant object replication. You can also use Azure Policy to enforce governance for a set of storage accounts. For example, you can create a policy with the deny effect to prevent a user from creating a storage account where the **AllowCrossTenantReplication** property is set to *true*, or from modifying an existing storage account to change the property value to *true*.
 
diff --git a/articles/storage/blobs/object-replication-prevent-cross-tenant-policies.md b/articles/storage/blobs/object-replication-prevent-cross-tenant-policies.md
diff --git a/articles/synapse-analytics/migration-guides/teradata/1-design-performance-migration.md b/articles/synapse-analytics/migration-guides/teradata/1-design-performance-migration.md
diff --git a/articles/synapse-analytics/sql-data-warehouse/backup-and-restore.md b/articles/synapse-analytics/sql-data-warehouse/backup-and-restore.md
diff --git a/articles/virtual-machines/managed-disks-overview.md b/articles/virtual-machines/managed-disks-overview.md
