Merge pull request #262120 from MicrosoftDocs/repo_sync_working_branch

Taojunshen · web-flow · commit 62f09905db0e · 2024-01-02T09:34:35.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/azure-functions/storage-considerations.md b/articles/azure-functions/storage-considerations.md
@@ -182,7 +182,7 @@ You can mount existing Azure Files shares to your Linux function apps. By mounti
 
 In this command, `share-name` is the name of the existing Azure Files share, and `custom-id` can be any string that uniquely defines the share when mounted to the function app. Also, `mount-path` is the path from which the share is accessed in your function app. `mount-path` must be in the format `/dir-name`, and it can't start with `/home`.
 
-For a complete example, see the scripts in [Create a Python function app and mount a Azure Files share](scripts/functions-cli-mount-files-storage-linux.md). 
+For a complete example, see the scripts in [Create a Python function app and mount an Azure Files share](scripts/functions-cli-mount-files-storage-linux.md). 
 
 # [Azure PowerShell](#tab/azure-powershell)
 
diff --git a/articles/azure-monitor/app/worker-service.md b/articles/azure-monitor/app/worker-service.md
@@ -33,7 +33,7 @@ You must have a valid Application Insights connection string. This string is req
     
     ```xml
         <ItemGroup>
-            <PackageReference Include="Microsoft.ApplicationInsights.WorkerService" Version="2.13.1" />
+            <PackageReference Include="Microsoft.ApplicationInsights.WorkerService" Version="2.22.0" />
         </ItemGroup>
     ```
 
diff --git a/articles/azure-resource-manager/bicep/user-defined-data-types.md b/articles/azure-resource-manager/bicep/user-defined-data-types.md
@@ -256,7 +256,7 @@ param serviceConfig ServiceConfig = { type: 'bar', value: true }
 output config object = serviceConfig
 ```
 
-The parameter value is validated based on the discriminated property value.  In the preceeding example, if the *serviceConfig* parameter value is of type *foo*, it undergoes validation using the *FooConfig*type. Likewise, if the parameter value is of type *bar*, validation is performed using the *BarConfig* type, and this pattern continues for other types as well.
+The parameter value is validated based on the discriminated property value.  In the preceding example, if the *serviceConfig* parameter value is of type *foo*, it undergoes validation using the *FooConfig*type. Likewise, if the parameter value is of type *bar*, validation is performed using the *BarConfig* type, and this pattern continues for other types as well.
 
 ## Import types between Bicep files (Preview)
 
diff --git a/articles/azure-resource-manager/management/resource-name-rules.md b/articles/azure-resource-manager/management/resource-name-rules.md
@@ -537,9 +537,9 @@ In the following tables, the term alphanumeric refers to:
 > [!div class="mx-tableFixed"]
 > | Entity | Scope | Length | Valid Characters |
 > | --- | --- | --- | --- |
-> | workspaces | resource group | 3-33 | Alphanumerics and hyphens |
+> | workspaces | resource group | 3-33 | Alphanumerics, hyphens, and underscores. |
 > | workspaces / computes | workspace | 3-24 for compute instance<br>3-32 for AML compute<br>2-16 for other compute types | Alphanumerics and hyphens. |
-> | workspaces / datastores | workspace | Maximum 255 characters for datastore name| Datastore name consists only of lowercase letters, digits, and underscores |
+> | workspaces / datastores | workspace | Maximum 255 characters for datastore name| Datastore name consists only of lowercase letters, digits, and underscores. |
 
 ## Microsoft.ManagedIdentity
 
diff --git a/articles/container-apps/dapr-component-resiliency.md b/articles/container-apps/dapr-component-resiliency.md
@@ -59,7 +59,7 @@ resource myPolicyDoc 'Microsoft.App/managedEnvironments/daprComponents/resilienc
             maxIntervalInMilliseconds: 10000
           }
       } 
-    }, 
+    } 
     inboundPolicy: {
       timeoutPolicy: {
         responseTimeoutInSeconds: 15
@@ -208,7 +208,7 @@ properties: {
     timeoutPolicy: {
         responseTimeoutInSeconds: 15
     }
-  },
+  }
   inbound: {
     timeoutPolicy: {
         responseTimeoutInSeconds: 15
@@ -236,7 +236,7 @@ properties: {
           maxIntervalInMilliseconds: 10000
         }
     }
-  },
+  }
   inbound: {
     httpRetryPolicy: {
         maxRetries: 5
diff --git a/articles/container-instances/container-instances-egress-ip-address.md b/articles/container-instances/container-instances-egress-ip-address.md
@@ -163,7 +163,7 @@ View the container logs to confirm the IP address is the same as the public IP a
 
 ```azurecli
 az container logs \
-  --sed 's/$RESOURCE_GROUP_NAME/$resourceGroup/g'
+  --resource-group $resourceGroup \
   --name testegress 
 ```
 
diff --git a/articles/cosmos-db/introduction.md b/articles/cosmos-db/introduction.md
@@ -19,7 +19,7 @@ Today's applications are required to be highly responsive and always online. To
 
 Recently, the surge of AI-powered applications created another layer of complexity, because many of these applications currently integrate a multitude of data stores. For example, some teams built applications that simultaneously connect to MongoDB, Postgres, and Gremlin. These databases differ in implementation workflow and operational performances, posing extra complexity for scaling applications. Azure Cosmos DB can simplify and expedite your development by being the single AI database for your applications. Azure Cosmos DB accommodates all your operational data models, including relational, document, vector, key-value, graph, and table.
 
-Azure Cosmos DB is a fully managed NoSQL and relational database for modern app development including; AI, digital commerce, Internet of Things, booking management, and other types of solutions. Azure Cosmos DB offers single-digit millisecond response times, automatic and instant scalability, along with guaranteed speed at any scale. Business continuity is assured with [SLA-backed](https://azure.microsoft.com/support/legal/sla/cosmos-db) availability and enterprise-grade security.
+Azure Cosmos DB is a fully managed NoSQL and relational database for modern app development including AI, digital commerce, Internet of Things, booking management, and other types of solutions. Azure Cosmos DB offers single-digit millisecond response times, automatic and instant scalability, along with guaranteed speed at any scale. Business continuity is assured with [SLA-backed](https://azure.microsoft.com/support/legal/sla/cosmos-db) availability and enterprise-grade security.
 
 App development is faster and more productive thanks to:
 
diff --git a/articles/databox-online/azure-stack-edge-gpu-manage-shares.md b/articles/databox-online/azure-stack-edge-gpu-manage-shares.md
@@ -69,7 +69,7 @@ Do the following steps in the Azure portal to create a share.
 3. Select a **Type** for the share. The type can be **SMB** or **NFS**, with SMB being the default. SMB is the standard for Windows clients, and NFS is used for Linux clients. Depending upon whether you choose SMB or NFS shares, options presented are slightly different.
 
    > [!IMPORTANT]
-   > Make sure that the Azure Storage account that you use doesn't have immutability policies set on it if you're using it with a Azure Stack Edge Pro or Data Box Gateway device. For more information, see [Set and manage immutability policies for blob storage](../storage/blobs/immutable-policy-configure-version-scope.md).
+   > Make sure that the Azure Storage account that you use doesn't have immutability policies set on it if you're using it with an Azure Stack Edge Pro or Data Box Gateway device. For more information, see [Set and manage immutability policies for blob storage](../storage/blobs/immutable-policy-configure-version-scope.md).
 
 4. To easily access the shares from Edge compute modules, use the local mount point. Select **Use the share with Edge compute** so that the Edge module can use the compute with the local mount point.
 
@@ -236,4 +236,4 @@ Do the following steps in the Azure portal to sync your storage access key.
 
 ## Next steps
 
-- Learn how to [Manage users via Azure portal](azure-stack-edge-gpu-manage-users.md).
+- Learn how to [Manage users via Azure portal](azure-stack-edge-gpu-manage-users.md).
diff --git a/articles/machine-learning/v1/azure-machine-learning-release-notes.md b/articles/machine-learning/v1/azure-machine-learning-release-notes.md
@@ -42,6 +42,7 @@ __RSS feed__: Get notified when this page is updated by copying and pasting the
     + Support of features/regressors known at the time of forecast in AutoML forecasting TCN models.
   + **azureml-core**
     + Add appinsights location swap for qatarcentral to point to uaenorth
+    + [Python 3.7 reached end-of-life on June 27th 2023](https://devguide.python.org/versions/). Consequently, 3.7 will be deprecated in azureml-core starting in October 2023 and azureml-core will end support for 3.7 in February 2024.
   + **azureml-mlflow**
     + Fix for loading models with MLflow load_model APIs when passing an AzureML URI
   + **azureml-pipeline-core**
diff --git a/articles/service-fabric/service-fabric-cluster-creation-setup-aad.md b/articles/service-fabric/service-fabric-cluster-creation-setup-aad.md
@@ -31,6 +31,10 @@ A Service Fabric cluster offers several entry points to its management functiona
 > [!NOTE]
 > Microsoft Entra ID now requires an application (app registration) publishers domain to be verified or use of default scheme. See [Configure an application's publisher domain](../active-directory/develop/howto-configure-publisher-domain.md) and [AppId Uri in single tenant applications will require use of default scheme or verified domains](../active-directory/develop/reference-breaking-changes.md#appid-uri-in-single-tenant-applications-will-require-use-of-default-scheme-or-verified-domains) for additional information.
 
+> [!NOTE]
+> Starting in Service Fabric 11.0, Service Fabric Explorer will require a Single-page application Redirect URI instead of a Web Redirect URI.
+
+
 ## Prerequisites
 
 In this article, we assume that you have already created a tenant. If you have not, start by reading [How to get a Microsoft Entra tenant][active-directory-howto-tenant].
@@ -61,7 +65,7 @@ Run `SetupApplications.ps1` and provide the tenant ID, cluster name, web applica
 
 - **clusterName:** *ClusterName* is used to prefix the Microsoft Entra applications that are created by the script. It does not need to match the actual cluster name exactly. It is intended only to make it easier to map Microsoft Entra artifacts to the Service Fabric cluster that they're being used with.
 
-- **webApplicationReplyUrl:** *WebApplicationReplyUrl* is the default endpoint that Microsoft Entra ID returns to your users after they finish signing in. Set this endpoint as the Service Fabric Explorer endpoint for your cluster. If you are creating Microsoft Entra applications to represent an existing cluster, make sure this URL matches your existing cluster's endpoint. If you are creating applications for a new cluster, plan the endpoint your cluster will have and make sure not to use the endpoint of an existing cluster. By default the Service Fabric Explorer endpoint is: `https://<cluster_domain>:19080/Explorer`
+- **SpaApplicationReplyUrl:** *SpaApplicationReplyUrl* is the default endpoint that Microsoft Entra ID returns to your users after they finish signing in. Set this endpoint as the Service Fabric Explorer endpoint for your cluster. If you are creating Microsoft Entra applications to represent an existing cluster, make sure this URL matches your existing cluster's endpoint. If you are creating applications for a new cluster, plan the endpoint your cluster will have and make sure not to use the endpoint of an existing cluster. By default the Service Fabric Explorer endpoint is: `https://<cluster_domain>:19080/Explorer/index.html`
 
 - **webApplicationUri:** *WebApplicationUri* is either the URI of a 'verified domain' or URI using API scheme format of api://{{tenant Id}}/{{cluster name}}. See [AppId Uri in single tenant applications will require use of default scheme or verified domains](../active-directory/develop/reference-breaking-changes.md#appid-uri-in-single-tenant-applications-will-require-use-of-default-scheme-or-verified-domains) for additional information.
 
@@ -78,13 +82,13 @@ Run `SetupApplications.ps1` and provide the tenant ID, cluster name, web applica
 
 $tenantId = '0e3d2646-78b3-4711-b8be-74a381d9890c'
 $clusterName = 'mysftestcluster'
-$webApplicationReplyUrl = 'https://mysftestcluster.eastus.cloudapp.azure.com:19080/Explorer/index.html' # <--- client browser redirect url
+$spaApplicationReplyUrl = 'https://mysftestcluster.eastus.cloudapp.azure.com:19080/Explorer/index.html' # <--- client browser redirect url
 #$webApplicationUri = 'https://mysftestcluster.contoso.com' # <--- must be verified domain due to AAD changes
 $webApplicationUri = "api://$tenantId/$clusterName" # <--- does not have to be verified domain
 
 $configObj = .\SetupApplications.ps1 -TenantId $tenantId `
   -ClusterName $clusterName `
-  -WebApplicationReplyUrl $webApplicationReplyUrl `
+  -SpaApplicationReplyUrl $spaApplicationReplyUrl `
   -AddResourceAccess `
   -WebApplicationUri $webApplicationUri `
   -Verbose
@@ -183,7 +187,7 @@ It may be necessary to 'Grant admin consent' for the 'API permissions' being con
 
 ## Verifying Microsoft Entra Configuration
 
-Navigate to the Service Fabric Explorer (SFX) URL. This should be the same as the parameter webApplicationReplyUrl. An Azure authentication dialog should be displayed. Log on with an account configured with the new Microsoft Entra configuration. Verify that the administrator account has read/write access and that the user has read access. Any modification to the cluster, for example, performing an action, is an administrative action.
+Navigate to the Service Fabric Explorer (SFX) URL. This should be the same as the parameter spaApplicationReplyUrl. An Azure authentication dialog should be displayed. Log on with an account configured with the new Microsoft Entra configuration. Verify that the administrator account has read/write access and that the user has read access. Any modification to the cluster, for example, performing an action, is an administrative action.
 
 
 <a name='troubleshooting-help-in-setting-up-azure-active-directory'></a>
diff --git a/articles/service-fabric/service-fabric-cluster-nodetypes.md b/articles/service-fabric/service-fabric-cluster-nodetypes.md
@@ -44,6 +44,7 @@ The following is a snippet of Service Fabric Virtual Machine extension:
     "properties": {
       "type": "ServiceFabricLinuxNode",
       "autoUpgradeMinorVersion": true,
+      "enableAutomaticUpgrade": true,
       "protectedSettings": {
         "StorageAccountKey1": "[listKeys(resourceId('Microsoft.Storage/storageAccounts', variables('supportLogStorageAccountName')),'2015-05-01-preview').key1]",
        },
@@ -62,7 +63,7 @@ The following is a snippet of Service Fabric Virtual Machine extension:
            "x509StoreName": "[parameters('certificateStoreValue')]"
          }
        },
-       "typeHandlerVersion": "1.1"
+       "typeHandlerVersion": "2.0"
      }
    },
 ```
@@ -72,8 +73,9 @@ The following are the property descriptions:
 | **Name** | **Allowed Values** | **Guidance or Short Description** |
 | --- | --- | --- | --- |
 | name | string | Unique name for extension |
-| type | "ServiceFabricLinuxNode" or "ServiceFabricWindowsNode" | Identifies OS Service Fabric is bootstrapping to |
-| autoUpgradeMinorVersion | true or false | Enable Auto Upgrade of SF Runtime Minor Versions |
+| type | "ServiceFabricLinuxNode" or "ServiceFabricNode" | Identifies OS Service Fabric is bootstrapping to |
+| autoUpgradeMinorVersion | true or false | Use newest minor version of extension at deployment time |
+| enableAutomaticUpgrade | true or false | Automatically upgrade extension once a non-major version is available. Only available for type ServiceFabricLinuxNode |
 | publisher | Microsoft.Azure.ServiceFabric | Name of the Service Fabric extension publisher |
 | clusterEndpoint | string | URI:PORT to Management endpoint |
 | nodeTypeRef | string | Name of nodeType |
diff --git a/articles/service-fabric/service-fabric-tutorial-create-vnet-and-linux-cluster.md b/articles/service-fabric/service-fabric-tutorial-create-vnet-and-linux-cluster.md
@@ -80,6 +80,43 @@ The names of the virtual network and subnet are declared in the template paramet
 
 If any other application ports are needed, then you will need to adjust the Microsoft.Network/loadBalancers resource to allow the traffic in.
 
+### Service Fabric Extension
+
+In the **Microsoft.Compute/virtualMachineScaleSets** resource, the Service Fabric Linux extension is configured. This extension is used to bootstrap Service Fabric to Azure Virtual Machines and configure Node Security.
+
+The following is a template snippet for the Service Fabric Linux extension:
+
+```json
+"extensions": [
+  {
+    "name": "[concat('ServiceFabricNodeVmExt','_vmNodeType0Name')]",
+    "properties": {
+      "type": "ServiceFabricLinuxNode",
+      "autoUpgradeMinorVersion": true,
+      "enableAutomaticUpgrade": true,
+      "protectedSettings": {
+        "StorageAccountKey1": "[listKeys(resourceId('Microsoft.Storage/storageAccounts', variables('supportLogStorageAccountName')),'2015-05-01-preview').key1]",
+       },
+       "publisher": "Microsoft.Azure.ServiceFabric",
+       "settings": {
+         "clusterEndpoint": "[reference(parameters('clusterName')).clusterEndpoint]",
+         "nodeTypeRef": "[variables('vmNodeType0Name')]",
+         "durabilityLevel": "Silver",
+         "enableParallelJobs": true,
+         "nicPrefixOverride": "[variables('subnet0Prefix')]",
+         "dataPath": "D:\\\\SvcFab",
+         "certificate": {
+           "commonNames": [
+             "[parameters('certificateCommonName')]"
+           ],
+           "x509StoreName": "[parameters('certificateStoreValue')]"
+         }
+       },
+       "typeHandlerVersion": "2.0"
+     }
+   },
+```
+
 ## Set template parameters
 
 The **AzureDeploy.Parameters** file declares many values used to deploy the cluster and associated resources. Some of the parameters that you might need to modify for your deployment:

Original file line number	Diff line number	Diff line change
`@@ -59,7 +59,7 @@ resource myPolicyDoc 'Microsoft.App/managedEnvironments/daprComponents/resilienc`
`59`	`59`	`maxIntervalInMilliseconds: 10000`
`60`	`60`	`}`
`61`	`61`	`}`
`62`		`- },`
	`62`	`+ }`
`63`	`63`	`inboundPolicy: {`
`64`	`64`	`timeoutPolicy: {`
`65`	`65`	`responseTimeoutInSeconds: 15`
`@@ -208,7 +208,7 @@ properties: {`
`208`	`208`	`timeoutPolicy: {`
`209`	`209`	`responseTimeoutInSeconds: 15`
`210`	`210`	`}`
`211`		`- },`
	`211`	`+ }`
`212`	`212`	`inbound: {`
`213`	`213`	`timeoutPolicy: {`
`214`	`214`	`responseTimeoutInSeconds: 15`
`@@ -236,7 +236,7 @@ properties: {`
`236`	`236`	`maxIntervalInMilliseconds: 10000`
`237`	`237`	`}`
`238`	`238`	`}`
`239`		`- },`
	`239`	`+ }`
`240`	`240`	`inbound: {`
`241`	`241`	`httpRetryPolicy: {`
`242`	`242`	`maxRetries: 5`