Merge pull request #285278 from MicrosoftDocs/repo_sync_working_branch

Taojunshen · web-flow · commit 04b84c010196 · 2024-08-23T00:31:59.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/document-intelligence/faq.yml b/articles/ai-services/document-intelligence/faq.yml
@@ -134,7 +134,15 @@ sections:
         answer: |
          **Yes.**
 
-         If your Document Intelligence resource is configured with a firewall or virtual network, you need to add the dedicated IP address 20.3.165.95 to the firewall allowlist for your Document Intelligence resource.
+         If your Document Intelligence resource is configured with a firewall or virtual network, you need to add the dedicated IP address 20.3.165.95 to the firewall allowlist for your Document Intelligence resource.  Please note that some functions in custom projects (e.g. auto-label, project management and human in the loop) won't work if the public network access is disabled.
+
+      - question: |
+         When I upload a file in Document Intelligence Studio by "Fetch from URL" function, can I use a URL from my blob storage?
+
+        answer: |
+         **Yes.** 
+         
+         If your Azure blob storage URL includes a SAS token and is accessible from public networks.  You cannot use the **Fetch** function for storage accounts where the key access is disabled or behind a firewall/VNet.
 
       - question: |
           Can I reuse or customize the labeling experience from Document Intelligence Studio and build it into my own application?
diff --git a/articles/ai-services/document-intelligence/managed-identities-secured-access.md b/articles/ai-services/document-intelligence/managed-identities-secured-access.md
@@ -114,7 +114,7 @@ To ensure that the Document Intelligence resource can access the training datase
 
     :::image type="content" source="media/managed-identities/v2-stg-role-assign-role.png" alt-text="Screenshot of add role assignment window.":::
 
-1. On the **Role** tab, search for and select the **Storage Blob Data Reader** permission and select **Next**.
+1. On the **Role** tab, search for and select the **Storage Blob Data Contributor** permission and select **Next**.
 
     :::image type="content" source="media/managed-identities/v2-stg-role-assignment.png" alt-text="Screenshot of choose a role tab.":::
 
@@ -279,7 +279,7 @@ That's it! You can now configure secure access for your Document Intelligence re
 
    :::image type="content" source="media/managed-identities/content-source-error.png" alt-text="Screenshot of content source not accessible error.":::
 
-    **Resolution**: Make sure you grant your Document Intelligence managed identity the role of **Storage Blob Data Reader** and enabled **Trusted services** access or **Resource instance** rules on the networking tab.
+    **Resolution**: Make sure you grant your Document Intelligence managed identity the role of **Storage Blob Data Contributor** and enabled **Trusted services** access or **Resource instance** rules on the networking tab.
 
 * **AccessDenied**:
 
diff --git a/articles/ai-services/document-intelligence/quickstarts/includes/javascript-sdk.md b/articles/ai-services/document-intelligence/quickstarts/includes/javascript-sdk.md
@@ -151,14 +151,14 @@ Extract text, selection marks, text styles, table structures, and bounding regio
   const { AzureKeyCredential } = require("@azure/core-auth");
 
     // set `<your-key>` and `<your-endpoint>` variables with the values from the Azure portal.
-    const key = "<your-key";
+    const key = "<your-key>";
     const endpoint = "<your-endpoint>";
 
     // sample document
     const formUrl = "https://raw.githubusercontent.com/Azure-Samples/cognitive-services-REST-api-samples/master/curl/form-recognizer/sample-layout.pdf"
 
    async function main() {
-    const client = DocumentIntelligence(endpoint, new AzureKeyCredential(key:key));
+    const client = DocumentIntelligence(endpoint, new AzureKeyCredential(key));
 
 
     const initialResponse = await client
@@ -329,7 +329,7 @@ const { AzureKeyCredential } = require("@azure/core-auth");
 
 async function main() {
 
-    const client = DocumentIntelligence(endpoint, new AzureKeyCredential(key:key));
+    const client = DocumentIntelligence(endpoint, new AzureKeyCredential(key));
 
     const initialResponse = await client
     .path("/documentModels/{modelId}:analyze", "prebuilt-invoice")
diff --git a/articles/ai-services/language-service/custom-named-entity-recognition/includes/roles-for-resource-and-storage.md b/articles/ai-services/language-service/custom-named-entity-recognition/includes/roles-for-resource-and-storage.md
@@ -37,5 +37,16 @@ Use the following steps to set the required roles for your Language resource and
 5. Select **Select members**
 6. Select your subscription, and **Language** as the managed identity. You can search for user names in the **Select** field. 
 
+### Roles for your user
+> [!IMPORTANT]
+> If you skip this step, you'll have a 403 error when trying to connect to your custom project. It's important that your current user has this role to access storage account blob data, even if you're the owner of the storage account.
+> 
+1. Go to your storage account page in the [Azure portal](https://portal.azure.com/).
+2. Select **Access Control (IAM)** in the left navigation menu.
+3. Select **Add** to **Add Role Assignments**, and choose the **Storage blob data contributor** role on the storage account.
+4. Within **Assign access to**, select **User, group, or service principal**. 
+5. Select **Select members**
+6. Select your User. You can search for user names in the **Select** field. 
+
 > [!IMPORTANT]
 > If you have a virtual network or private endpoint, be sure to select **Allow Azure services on the trusted services list to access this storage account** in the Azure portal.
diff --git a/articles/ai-services/language-service/custom-text-classification/concepts/data-formats.md b/articles/ai-services/language-service/custom-text-classification/concepts/data-formats.md
@@ -27,39 +27,40 @@ Your Labels file should be in the `json` format below. This will enable you to [
     "projectFileVersion": "2022-05-01",
     "stringIndexType": "Utf16CodeUnit",
     "metadata": {
-      "projectKind": "CustomMultiLabelClassification",
-      "storageInputContainerName": "{CONTAINER-NAME}",
-      "projectName": "{PROJECT-NAME}",
-      "multilingual": false,
-      "description": "Project-description",
-      "language": "en-us"
+        "projectKind": "CustomMultiLabelClassification",
+        "storageInputContainerName": "{CONTAINER-NAME}",
+        "projectName": "{PROJECT-NAME}",
+        "multilingual": false,
+        "description": "Project-description",
+        "language": "en-us"
     },
     "assets": {
-      "projectKind": "CustomMultiLabelClassification",
-      "classes": [
-        {
-          "category": "Class1"
-        },
-        {
-          "category": "Class2"
-        }
-      ],
-      "documents": [
-          {
-              "location": "{DOCUMENT-NAME}",
-              "language": "{LANGUAGE-CODE}",
-              "dataset": "{DATASET}",
-              "classes": [
-                  {
-                      "category": "Class1"
-                  },
-                  {
-                      "category": "Class2"
-                  }
-              ]
-          }
-      ]
-  }
+        "projectKind": "CustomMultiLabelClassification",
+        "classes": [
+            {
+                "category": "Class1"
+            },
+            {
+                "category": "Class2"
+            }
+        ],
+        "documents": [
+            {
+                "location": "{DOCUMENT-NAME}",
+                "language": "{LANGUAGE-CODE}",
+                "dataset": "{DATASET}",
+                "classes": [
+                    {
+                        "category": "Class1"
+                    },
+                    {
+                        "category": "Class2"
+                    }
+                ]
+            }
+        ]
+    }
+}
 ```
 
 |Key  |Placeholder  |Value  | Example |
@@ -81,43 +82,44 @@ Your Labels file should be in the `json` format below. This will enable you to [
     "projectFileVersion": "2022-05-01",
     "stringIndexType": "Utf16CodeUnit",
     "metadata": {
-      "projectKind": "CustomSingleLabelClassification",
-      "storageInputContainerName": "{CONTAINER-NAME}",
-      "settings": {},
-      "projectName": "{PROJECT-NAME}",
-      "multilingual": false,
-      "description": "Project-description",
-      "language": "en-us"
+        "projectKind": "CustomSingleLabelClassification",
+        "storageInputContainerName": "{CONTAINER-NAME}",
+        "settings": {},
+        "projectName": "{PROJECT-NAME}",
+        "multilingual": false,
+        "description": "Project-description",
+        "language": "en-us"
     },
     "assets": {
-      "projectKind": "CustomSingleLabelClassification",
-      "classes": [
-          {
-              "category": "Class1"
-          },
-          {
-              "category": "Class2"
-          }
-      ],
-      "documents": [
-          {
-              "location": "{DOCUMENT-NAME}",
-              "language": "{LANGUAGE-CODE}",
-              "dataset": "{DATASET}",
-              "class": {
-                  "category": "Class2"
-              }
-          },
-          {
-              "location": "{DOCUMENT-NAME}",
-              "language": "{LANGUAGE-CODE}",
-              "dataset": "{DATASET}",
-              "class": {
-                  "category": "Class1"
-              }
-          }
-      ]
-  }
+        "projectKind": "CustomSingleLabelClassification",
+        "classes": [
+            {
+                "category": "Class1"
+            },
+            {
+                "category": "Class2"
+            }
+        ],
+        "documents": [
+            {
+                "location": "{DOCUMENT-NAME}",
+                "language": "{LANGUAGE-CODE}",
+                "dataset": "{DATASET}",
+                "class": {
+                    "category": "Class2"
+                }
+            },
+            {
+                "location": "{DOCUMENT-NAME}",
+                "language": "{LANGUAGE-CODE}",
+                "dataset": "{DATASET}",
+                "class": {
+                    "category": "Class1"
+                }
+            }
+        ]
+    }
+}
 ```
 |Key  |Placeholder  |Value  | Example |
 |---------|---------|----------|--|
diff --git a/articles/azure-monitor/agents/azure-monitor-agent-extension-versions.md b/articles/azure-monitor/agents/azure-monitor-agent-extension-versions.md
@@ -23,7 +23,7 @@ We strongly recommended to always update to the latest version, or opt in to the
 ## Version details
 | Release Date | Release notes | Windows | Linux |
 |:---|:---|:---|:---|
-| August 2024      | **Windows**<ul><li>Added columns to the SecurityEvent table: Keywords, Opcode, Correlation, ProcessId, ThreadId, EventRecordId.</li><li>AMA: Support AMA Client Installer for selected partners.</li></ul>**Linux Features**<ul><li>Enable Dynamic Linking of OpenSSL 1.1 in all regions</li><li>Add Computer field to Custom Logs</li><li>Add EventHub upload support for Custom Logs </li><li>Reliability improvement for upload task scheduling</li><li>Added support for SUSE15 SP5, and AWS 3 distributions</li></ul>**Linux Fixes**<ul><li>Fix Direct upload to storage for perf counters when no other destination is configured. You don't see perf counters If storage was the only configured destination for perf counters, they wouldn't see perf counters in their blob or table.</li><li>Fluent-Bit updated to version 3.0.7. This fixes the issue with Fluent-Bit creating junk files in the root directory on process shutdown.</li><li>Fix proxy for system-wide proxy using http(s)_proxy env var </li><li>Support for syslog hostnames that are up to 255characters</li><li>Stop sending rows longer than 1MB. This exceeds ingestion limits and destabilizes the agent. Now the row is gracefully dropped and a diagnostic message is written.</li><li>Set max disk space used for rsyslog spooling to 1GB. There was no limit before which could lead to high memory usage.</li><li>Use random available TCP port when there is a port conflict with AMA port 28230 and 28330 . This resolved issues where port 28230 and 28330 were already in uses by the customer which prevented data upload to Azure.</li></ul>| 1.29 | 1.32.5 |
+| August 2024      | **Windows**<ul><li>Added columns to the SecurityEvent table: Keywords, Opcode, Correlation, ProcessId, ThreadId, EventRecordId.</li><li>AMA: Support AMA Client Installer for selected partners.</li></ul>**Linux Features**<ul><li>Enable Dynamic Linking of OpenSSL 1.1 in all regions</li><li>Add Computer field to Custom Logs</li><li>Add EventHub upload support for Custom Logs </li><li>Reliability improvement for upload task scheduling</li><li>Added support for SUSE15 SP5, and AWS 3 distributions</li></ul>**Linux Fixes**<ul><li>Fix Direct upload to storage for perf counters when no other destination is configured. You don't see perf counters If storage was the only configured destination for perf counters, they wouldn't see perf counters in their blob or table.</li><li>Fluent-Bit updated to version 3.0.7. This fixes the issue with Fluent-Bit creating junk files in the root directory on process shutdown.</li><li>Fix proxy for system-wide proxy using http(s)_proxy env var </li><li>Support for syslog hostnames that are up to 255characters</li><li>Stop sending rows longer than 1MB. This exceeds ingestion limits and destabilizes the agent. Now the row is gracefully dropped and a diagnostic message is written.</li><li>Set max disk space used for rsyslog spooling to 1GB. There was no limit before which could lead to high memory usage.</li><li>Use random available TCP port when there is a port conflict with AMA port 28230 and 28330 . This resolved issues where port 28230 and 28330 were already in uses by the customer which prevented data upload to Azure.</li></ul>| 1.29 | 1.32.6 |
 | June 2024      |**Windows**<ul><li>Fix encoding issues with Resource ID field.</li><li>AMA: Support new ingestion endpoint for GovSG environment.</li><li>Upgrade AzureSecurityPack version to 4.33.0.1.</li><li>Upgrade Metrics Extension version to 2.2024.517.533.</li><li>Upgrade Health Extension version to 2024.528.1.</li></ul>**Linux**<ul><li>Coming Soon</li></ul>| 1.28.2 | |
 | May 2024      |**Windows**<ul><li>Upgraded Fluent-bit version to 3.0.5. This Fix resolves as security issue in fluent-bit (NVD - CVE-2024-4323 (nist.gov)</li><li>Disabled Fluent-bit logging that caused disk exhaustion issues for some customers. Example error is Fluentbit log with "[C:\projects\fluent-bit-2e87g\src\flb_scheduler.c:72 errno=0] No error" fills up the entire disk of the server.</li><li>Fixed AMA extension getting stuck in deletion state on some VMs that are using Arc. This fix improves reliability.</li><li>Fixed AMA not using system proxy, this issue is a bug introduced in 1.26.0. The issue was caused by a new feature that uses the Arc agent’s proxy settings. When the system proxy as set as None the proxy was broken in 1.26.</li><li>Fixed Windows Firewall Logs log file rollover issues</li></ul>| 1.27.0 | |
 | April 2024    |**Windows**<ul><li>In preparation for the May 17 public preview of Firewall Logs, the agent completed the addition of a profile filter for Domain, Public, and Private Logs. </li><li>AMA running on an Arc enabled server will default to using the Arc proxy settings if available.</li><li>The AMA VM extension proxy settings override the Arc defaults.</li><li>Bug fix in MSI installer: Symptom - If there are spaces in the fluent-bit config path, AMA wasn't recognizing the path properly. AMA now adds quotes to configuration path in fluent-bit.</li><li>Bug fix for Container Insights: Symptom - custom resource ID weren't being honored.</li><li>Security issue fix: skip the deletion of files and directory whose path contains a redirection (via Junction point, Hard links, Mount point, OB Symlinks etc.).</li><li>Updating MetricExtension package to 2.2024.328.1744.</li></ul>**Linux**<ul><li>AMA 1.30 now available in Arc.</li><li>New distribution support Debian 12, RHEL CIS L2.</li><li>Fix for mdsd version 1.30.3 in persistence mode, which converted positive integers to float/double values ("3.0", "4.0") to type ulong which broke Azure stream analytics.</li></ul>| 1.26.0 | 1.31.1 |
diff --git a/articles/backup/manage-monitor-sql-database-backup.md b/articles/backup/manage-monitor-sql-database-backup.md
@@ -122,7 +122,7 @@ You can run different types of on-demand backups:
 >The retention period of this backup is determined by the type of on-demand backup you have run.
 >
 >- *On-demand full* retains backups for a minimum of *45 days* and a maximum of *99 years*.
->- *On-demand copy only full* accepts any v0alue for retaintion.
+>- *On-demand copy only full* accepts any value for retaintion.
 >- *On-demand differential* retains backup as per the retention of scheduled differentials set in policy.
 >- *On-demand log* retains backups as per the retention of scheduled logs set in policy.
 
@@ -200,4 +200,4 @@ Different           | Same or different        | Same or different     | Same or
 
 ## Next steps
 
-For more information, see [Troubleshoot backups on a SQL Server database](backup-sql-server-azure-troubleshoot.md).
+For more information, see [Troubleshoot backups on a SQL Server database](backup-sql-server-azure-troubleshoot.md).
diff --git a/articles/networking/nva-accelerated-connections.md b/articles/networking/nva-accelerated-connections.md
@@ -71,6 +71,13 @@ This list will be updated as more regions become available. The following region
 * South UK
 * West Europe
 * Central India
+* West US 2
+* West US 3
+* North Europe
+* Central Sweden
+* Southeast Asia
+* South US
+* East Australia
 
 ## Supported SKUs
 
