Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into updatevmss

siddomala · siddomala · commit 20d8525f8cc6 · 2023-09-11T12:00:29.000-07:00
diff --git a/articles/active-directory/azuread-dev/active-directory-authentication-libraries.md b/articles/active-directory/azuread-dev/active-directory-authentication-libraries.md
@@ -38,7 +38,7 @@ The Azure Active Directory Authentication Library (ADAL) v1.0 enables applicatio
 | --- | --- | --- | --- | --- | --- |
 | .NET Client, Windows Store, UWP, Xamarin iOS and Android |ADAL .NET v3 |[NuGet](https://www.nuget.org/packages/Microsoft.IdentityModel.Clients.ActiveDirectory) |[GitHub](https://github.com/AzureAD/azure-activedirectory-library-for-dotnet) | [Desktop app](../develop/quickstart-v2-windows-desktop.md) | |
 | JavaScript |ADAL.js |[GitHub](https://github.com/AzureAD/azure-activedirectory-library-for-js) |[GitHub](https://github.com/AzureAD/azure-activedirectory-library-for-js) |[Single-page app](https://github.com/Azure-Samples/active-directory-javascript-singlepageapp-dotnet-webapi) | |
-| iOS, macOS |ADAL |[GitHub](https://github.com/AzureAD/azure-activedirectory-library-for-objc/releases) |[GitHub](https://github.com/AzureAD/azure-activedirectory-library-for-objc) |[iOS app](../develop/quickstart-v2-ios.md) | [Reference](http://cocoadocs.org/docsets/ADAL/2.5.1/)|
+| iOS, macOS |ADAL |[GitHub](https://github.com/AzureAD/azure-activedirectory-library-for-objc/releases) |[GitHub](https://github.com/AzureAD/azure-activedirectory-library-for-objc) |[iOS app](../develop/quickstart-v2-ios.md) | |
 | Android |ADAL |[Maven](https://search.maven.org/search?q=g:com.microsoft.aad+AND+a:adal&core=gav) |[GitHub](https://github.com/AzureAD/azure-activedirectory-library-for-android) |[Android app](../develop/quickstart-v2-android.md) | [JavaDocs](https://javadoc.io/doc/com.microsoft.aad/adal/)|
 | Node.js |ADAL |[npm](https://www.npmjs.com/package/adal-node) |[GitHub](https://github.com/AzureAD/azure-activedirectory-library-for-nodejs) | [Node.js web app](https://github.com/Azure-Samples/active-directory-node-webapp-openidconnect)|[Reference](/javascript/api/overview/azure/active-directory) |
 | Java |ADAL4J |[Maven](https://search.maven.org/#search%7Cga%7C1%7Ca%3Aadal4j%20g%3Acom.microsoft.azure) |[GitHub](https://github.com/AzureAD/azure-activedirectory-library-for-java) |[Java web app](https://github.com/Azure-Samples/active-directory-java-webapp-openidconnect) |[Reference](https://javadoc.io/doc/com.microsoft.azure/adal4j) |
diff --git a/articles/active-directory/saas-apps/uni-tel-as-provisioning-tutorial.md b/articles/active-directory/saas-apps/uni-tel-as-provisioning-tutorial.md
@@ -16,7 +16,7 @@ ms.author: thwimmer
 
 # Tutorial: Configure Uni-tel A/S for automatic user provisioning
 
-This tutorial describes the steps you need to perform in both Uni-tel A/S and Azure Active Directory (Azure AD) to configure automatic user provisioning. When configured, Azure AD automatically provisions and de-provisions users to [Uni-tel A/S](https://beta-dashboard.one-connect.dk) using the Azure AD Provisioning service. For important details on what this service does, how it works, and frequently asked questions, see [Automate user provisioning and deprovisioning to SaaS applications with Azure Active Directory](../app-provisioning/user-provisioning.md). 
+This tutorial describes the steps you need to perform in both Uni-tel A/S and Azure Active Directory (Azure AD) to configure automatic user provisioning. When configured, Azure AD automatically provisions and de-provisions users to [Uni-tel A/S](https://uni-tel.dk/) using the Azure AD Provisioning service. For important details on what this service does, how it works, and frequently asked questions, see [Automate user provisioning and deprovisioning to SaaS applications with Azure Active Directory](../app-provisioning/user-provisioning.md). 
 
 
 ## Supported capabilities
diff --git a/articles/azure-fluid-relay/concepts/version-compatibility.md b/articles/azure-fluid-relay/concepts/version-compatibility.md
@@ -40,7 +40,6 @@ npx install-peerdeps @fluidframework/azure-client
 | @fluidframework/azure-client        | [1.0.2][]      | [API](https://fluidframework.com/docs/apis/azure-client/)        |
 | fluid-framework                     | [1.2.4][]      | [API](https://fluidframework.com/docs/apis/fluid-framework/)     |
 | @fluidframework/azure-service-utils | [1.0.2][]      | [API](https://fluidframework.com/docs/apis/azure-service-utils/) |
-| @fluidframework/test-client-utils   | [1.2.4][]      | [API](https://fluidframework.com/docs/apis/test-client-utils/)   |
 
 [1.0.2]: https://fluidframework.com/docs/updates/v1.0.0/
 [1.2.4]: https://fluidframework.com/docs/updates/v1.0.0/
diff --git a/articles/azure-functions/dotnet-isolated-process-guide.md b/articles/azure-functions/dotnet-isolated-process-guide.md
@@ -229,6 +229,7 @@ Placeholders are a platform capability that improves cold start. Normally, you d
 
 - Set the `WEBSITE_USE_PLACEHOLDER_DOTNETISOLATED` application setting to "1"
 - Ensure that the `netFrameworkVersion` property of the function app matches your project's target framework, which must be .NET 6 or later.
+- Ensure that the function app is configured to use a 64-bit process.
 - Update your project file:
     - Upgrade [Microsoft.Azure.Functions.Worker] to version 1.19.0 or later
     - Upgrade [Microsoft.Azure.Functions.Worker.Sdk] to version 1.14.1 or later
@@ -239,11 +240,12 @@ Placeholders are a platform capability that improves cold start. Normally, you d
 > [!NOTE]
 > Setting `FunctionsEnableWorkerIndexing` to "True" may cause an issue when debugging locally using version 4.0.5274 or earlier of the [Azure Functions Core Tools](./functions-run-local.md). The issue manifests with the debugger not being able to attach. If you encounter this issue, remove the `FunctionsEnableWorkerIndexing` property during local testing.
 
-The following CLI commands will set the application setting and update the `netFrameworkVersion` property. Replace `<groupName>` with the name of the resource group, and replace `<appName>` with the name of your function app. Replace `<framework>` with the appropriate version string, such as "v6.0" or "v7.0", according to your target .NET version.
+The following CLI commands will set the application setting, update the `netFrameworkVersion` property, and make the app run as 64-bit. Replace `<groupName>` with the name of the resource group, and replace `<appName>` with the name of your function app. Replace `<framework>` with the appropriate version string, such as "v6.0" or "v7.0", according to your target .NET version.
 
 ```azurecli
 az functionapp config appsettings set -g <groupName> -n <appName> --settings 'WEBSITE_USE_PLACEHOLDER_DOTNETISOLATED=1'
 az functionapp config set -g <groupName> -n <appName> --net-framework-version <framework>
+az functionapp config set -g <groupName> -n <appName> --use-32bit-worker-process false
 ```
 
 The following example shows a project file with the appropriate changes in place:
@@ -326,34 +328,42 @@ You can compile your function app as [ReadyToRun binaries](/dotnet/core/deployin
 
 ReadyToRun requires you to build the project against the runtime architecture of the hosting app. **If these are not aligned, your app will encounter an error at startup.** Select your runtime identifier from the table below:
 
-|Operating System | App is 32-bit | Runtime identifier |
+|Operating System | App is 32-bit<sup>1</sup> | Runtime identifier |
 |-|-|-|
 | Windows | True | `win-x86` |
 | Windows | False | `win-x64` |
 | Linux | True | N/A (not supported) |
 | Linux | False | `linux-x64` | 
 
+<sup>1</sup> Only 64-bit apps are eligible for some other performance optimizations such as [placeholders](#placeholders-preview).
+
 To check if your Windows app is 32-bit or 64-bit, you can run the following CLI command, substituting `<group_name>` with the name of your resource group and `<app_name>` with the name of your application. An output of "true" indicates that the app is 32-bit, and "false" indicates 64-bit.
 
 ```azurecli
  az functionapp config show -g <group_name> -n <app_name> --query "use32BitWorkerProcess"
 ```
 
-To compile your project as ReadyToRun, update your project file by adding the `<PublishReadyToRun>` and `<RuntimeIdentifier>` elements. The following examples shows a configuration for publishing to a Windows 32-bit function app.
+You can change your application to 64-bit with the following command, using the same substitutions:
+
+```azurecli
+az functionapp config set -g <group_name> -n <app_name> --use-32bit-worker-process false`
+```
+
+To compile your project as ReadyToRun, update your project file by adding the `<PublishReadyToRun>` and `<RuntimeIdentifier>` elements. The following examples shows a configuration for publishing to a Windows 64-bit function app.
 
 ```xml
 <PropertyGroup>
   <TargetFramework>net6.0</TargetFramework>
   <AzureFunctionsVersion>v4</AzureFunctionsVersion>
-  <RuntimeIdentifier>win-x86</RuntimeIdentifier>
+  <RuntimeIdentifier>win-x64</RuntimeIdentifier>
   <PublishReadyToRun>true</PublishReadyToRun>
 </PropertyGroup>
 ```
 
-If you don't want to set the `<RuntimeIdentifier>` as part of the project file, you can also configure this as part of the publish gesture itself. For example, with a Windows 32-bit function app, the .NET CLI command would be:
+If you don't want to set the `<RuntimeIdentifier>` as part of the project file, you can also configure this as part of the publish gesture itself. For example, with a Windows 64-bit function app, the .NET CLI command would be:
 
 ```dotnetcli
-dotnet publish --runtime win-x86
+dotnet publish --runtime win-x64
 ```
 
 In Visual Studio, the "Target Runtime" option in the publish profile should be set to the correct runtime identifier. If it is set to the default value "Portable", ReadyToRun will not be used.
diff --git a/articles/azure-government/documentation-government-csp-list.md b/articles/azure-government/documentation-government-csp-list.md
@@ -413,7 +413,6 @@ Below you can find a list of all the authorized Cloud Solution Providers (CSPs),
 |[StoneFly, Inc.](https://stonefly.com)|
 |[Strategic Communications](https://stratcomminc.com)|
 |[Stratus Solutions](https://stratussolutions.com)|
-|[Stratum Technology Manamgent, LLC](https://www.stratumtechnology.com)|
 |[Strongbridge LLC](https://www.sb-llc.com)|
 |[Summit 7 Systems, Inc.](https://www.summit7.us/)|
 |[Sumo Logic](https://www.sumologic.com/)|
diff --git a/articles/azure-monitor/partners.md b/articles/azure-monitor/partners.md
@@ -66,7 +66,7 @@ See the [Botmetric introduction for Azure](https://nutanix.medium.com/announcing
 
 Circonus provides a platform for machine data intelligence that can handle billions of metric streams in real time to drive business insight and value. Use Circonus to collect, track, and visualize key metrics related to your Microsoft Azure setup. Gain system-wide visibility into Azure resource utilization, application performance, and operational health.
 
-For more information, see the [Circonus documentation](https://docs.circonus.com/circonus/agents/cloud-agent/azure/).
+For more information, see the [Circonus documentation](https://docs.circonus.com/circonus3/integrations/agents/circonus-cloud-agent/#azure).
 
 ## CloudHealth
 
diff --git a/articles/cosmos-db/partners-migration.md b/articles/cosmos-db/partners-migration.md
@@ -30,7 +30,6 @@ From NoSQL migration to application development, you can choose from a variety o
 | [Cognizant](https://www.cognizant.com/) | IoT, Personalization, Retail (inventory), Operational Analytics (Spark), App development | USA, Canada, UK, Denmark, Netherlands, Switzerland, Australia, Japan |
 | [Infosys](https://www.infosys.com/) | App development | USA |
 | [Lambda3 Informatics](https://www.lambda3.com.br/) | Real-time personalization, Retail inventory, App development | Brazil |
-| [Neal Analytics](https://www.nealanalytics.com/) | Personalization, Retail (inventory), Operational Analytics (Spark), App development | USA |
 | [Pragmatic Works Software Inc](https://www.pragmaticworks.com/) | NoSQL migration | USA |
 | [Ricoh Digital Experience](https://www.ricoh-europe.com/contact-us) | IoT, Real-time personalization, Retail inventory, NoSQL migration | UK, Europe |
 | [SNP Technologies](https://www.snp.com/) | NoSQL migration | USA |
diff --git a/articles/dns/private-resolver-endpoints-rulesets.md b/articles/dns/private-resolver-endpoints-rulesets.md
@@ -6,7 +6,7 @@ author: greg-lindsay
 ms.service: dns
 ms.custom: ignite-2022
 ms.topic: conceptual
-ms.date: 08/07/2023
+ms.date: 09/11/2023
 ms.author: greglin
 #Customer intent: As an administrator, I want to understand components of the Azure DNS Private Resolver.
 ---
@@ -106,7 +106,7 @@ A query for `secure.store.azure.contoso.com` matches the **AzurePrivate** rule f
 #### Rule processing
 
 - If multiple DNS servers are entered as the destination for a rule, the first IP address that is entered is used unless it doesn't respond. An exponential backoff algorithm is used to determine whether or not a destination IP address is responsive. Destination addresses that are marked as unresponsive aren't used for 30 minutes.
-- Certain domains are ignored when using a wildcard rule for DNS resolution, because they are reserved for Azure services. See [Azure services DNS zone configuration](../private-link/private-endpoint-dns.md#azure-services-dns-zone-configuration) for a list of domains that are reserved. The two-label DNS names listed in this article (ex: windows.net, azure.com, azure.net, windowsazure.us) are reserved for Azure services.
+- Certain domains are ignored when using a wildcard rule for DNS resolution, because they are reserved for Azure services. See [Azure services DNS zone configuration](../private-link/private-endpoint-dns.md#azure-services-dns-zone-configuration) for a list of domains that are reserved. The two-label DNS names listed in this article (for example: windows.net, azure.com, azure.net, windowsazure.us) are reserved for Azure services.
 
 > [!IMPORTANT]
 > - You can't enter the Azure DNS IP address of 168.63.129.16 as the destination IP address for a rule. Attempting to add this IP address will output the error: **Exception while making add request for rule**. 
diff --git a/articles/genomics/quickstart-run-genomics-workflow-portal.md b/articles/genomics/quickstart-run-genomics-workflow-portal.md
@@ -104,10 +104,7 @@ Then select **Review + create** to create your storage account. As you did with
 
 ## Upload input data to your storage account
 
-The Microsoft Genomics service expects paired end reads (fastq or bam files) as input files. You can choose to either upload your own data, or explore using publicly available sample data provided for you. If you would like to use the publicly available sample data, it is hosted here:
-
-[https://msgensampledata.blob.core.windows.net/small/chr21_1.fq.gz](https://msgensampledata.blob.core.windows.net/small/chr21_1.fq.gz)
-[https://msgensampledata.blob.core.windows.net/small/chr21_2.fq.gz](https://msgensampledata.blob.core.windows.net/small/chr21_2.fq.gz)
+The Microsoft Genomics service expects paired end reads (fastq or bam files) as input files. You can choose to either upload your own data, or explore using publicly available sample data provided for you.
 
 Within your storage account, you need to make one blob container for your input data and a second blob container for your output data.  Upload the input data into your input blob container. Various tools can be used to do this, including [Microsoft Azure Storage Explorer](https://azure.microsoft.com/features/storage-explorer/), [BlobPorter](https://github.com/Azure/blobporter), or [AzCopy](../storage/common/storage-use-azcopy-v10.md?toc=%2fazure%2fstorage%2fblobs%2ftoc.json). 
 
diff --git a/articles/hdinsight/hdinsight-os-patching.md b/articles/hdinsight/hdinsight-os-patching.md
@@ -21,8 +21,7 @@ HDInsight provides support for you to perform common tasks on your cluster such
 > Script actions won't automatically apply updates for all future update cycles. Run the scripts each time new updates must be applied to install the updates, and then restart the VM.
 > 
 > If you are using a firewall for network restriction, the below URL needs to be in allow list. 
-> * http://security.ubuntu.com/ubuntu 
-> * https://hdiconfigactions.blob.core.windows.net
+> * http://security.ubuntu.com/ubuntu
 
 ## Preparation
 
diff --git a/articles/logic-apps/logic-apps-content-type.md b/articles/logic-apps/logic-apps-content-type.md
@@ -118,8 +118,7 @@ reference and use those properties more easily in your logic app's workflow.
      }
      ```
 
-  3. In your request, make sure you include a `Content-Type` header 
-  and set the header's value to `application/json`.
+  3. In the HTTP request that your client app sends to Azure Logic Apps, make sure that you include a header named **Content-Type**, and set the header's value to **application/json**.
 
 * **Parse JSON action**
 
diff --git a/articles/open-datasets/dataset-san-francisco-safety.md b/articles/open-datasets/dataset-san-francisco-safety.md
@@ -32,10 +32,6 @@ This dataset is stored in the East US Azure region. Allocating compute resources
 - [Fire Department Calls](https://data.sfgov.org/Public-Safety/Fire-Department-Calls-for-Service/nuek-vuh3)
 - [311 Cases](https://data.sfgov.org/City-Infrastructure/311-Cases/vw6y-z8j6)
 
-## Additional information
-
-This dataset is sourced from city of San Francisco government. See the [terms of using this dataset](https://datasf.org/opendata/terms-of-use/).
-
 ## Columns
 
 | Name | Data type | Unique | Values (sample) | Description |
diff --git a/articles/service-fabric/service-fabric-cluster-creation-for-windows-server.md b/articles/service-fabric/service-fabric-cluster-creation-for-windows-server.md
@@ -170,9 +170,9 @@ This script can be run on any machine that has administrator access to all the m
 <a id="telemetry"></a>
 
 ## Telemetry data collected and how to opt out of it
-As a default, the product collects telemetry on the Service Fabric usage to improve the product. The Best Practice Analyzer that runs as a part of the setup checks for connectivity to [https://vortex.data.microsoft.com/collect/v1](https://vortex.data.microsoft.com/collect/v1). If it is not reachable, the setup fails unless you opt out of telemetry.
+As a default, the product collects telemetry on the Service Fabric usage to improve the product. If it is not reachable, the setup fails unless you opt out of telemetry.
 
-1. The telemetry pipeline tries to upload the following data to [https://vortex.data.microsoft.com/collect/v1](https://vortex.data.microsoft.com/collect/v1) once every day. It is a best-effort upload and has no impact on the cluster functionality. The telemetry is only sent from the node that runs the failover manager primary. No other nodes send out telemetry.
+1. It is a best-effort upload and has no impact on the cluster functionality. The telemetry is only sent from the node that runs the failover manager primary. No other nodes send out telemetry.
 2. The telemetry consists of the following:
 
 * Number of services
diff --git a/articles/service-fabric/service-fabric-containers-volume-logging-drivers.md b/articles/service-fabric/service-fabric-containers-volume-logging-drivers.md
@@ -199,7 +199,7 @@ As shown in the **DriverOption** elements in the snippet above, the Azure Files
 ## Using your own volume or logging driver
 Service Fabric also allows the usage of your own custom [volume](https://docs.docker.com/engine/extend/plugins_volume/) or [logging](https://docs.docker.com/engine/admin/logging/overview/) drivers. If the Docker volume/logging driver is not installed on the cluster, you can install it manually by using the RDP/SSH protocols. You can perform the install with these protocols through a [virtual machine scale set start-up script](https://azure.microsoft.com/resources/templates/vmss-custom-script-windows/) or an [SetupEntryPoint script](./service-fabric-application-model.md).
 
-An example of the script to install the [Docker volume driver for Azure](https://docs.docker.com/docker-for-azure/persistent-data-volumes/) is as follows:
+An example of the script to install the [Docker volume driver for Azure](https://docs.docker.com/cloud/aci-compose-features/) is as follows:
 
 ```bash
 docker plugin install --alias azure --grant-all-permissions docker4x/cloudstor:17.09.0-ce-azure1  \
diff --git a/articles/service-fabric/service-fabric-reliable-services-communication-remoting.md b/articles/service-fabric/service-fabric-reliable-services-communication-remoting.md
@@ -90,7 +90,7 @@ Service proxy creation is a lightweight operation, so you can create as many as
 ### Service proxy factory lifetime
 
 [ServiceProxyFactory](/dotnet/api/microsoft.servicefabric.services.remoting.client.serviceproxyfactory) is a factory that creates proxy instances for different remoting interfaces. If you use the API `ServiceProxyFactory.CreateServiceProxy` to create a proxy, the framework creates a singleton service proxy.
-It is useful to create one manually when you need to override [IServiceRemotingClientFactory](/dotnet/api/microsoft.servicefabric.services.remoting.v1.client.iserviceremotingclientfactory) properties.
+It is useful to create one manually when you need to override IServiceRemotingClientFactory properties.
 Factory creation is an expensive operation. A service proxy factory maintains an internal cache of the communication client.
 A best practice is to cache the service proxy factory for as long as possible.
 
diff --git a/includes/functions-dotnet-migrate-v4-versions.md b/includes/functions-dotnet-migrate-v4-versions.md
diff --git a/includes/functions-dotnet-supported-versions.md b/includes/functions-dotnet-supported-versions.md

Original file line number	Diff line number	Diff line change
`@@ -21,8 +21,7 @@ HDInsight provides support for you to perform common tasks on your cluster such`
`21`	`21`	`> Script actions won't automatically apply updates for all future update cycles. Run the scripts each time new updates must be applied to install the updates, and then restart the VM.`
`22`	`22`	`>`
`23`	`23`	`> If you are using a firewall for network restriction, the below URL needs to be in allow list.`
`24`		`-> * http://security.ubuntu.com/ubuntu`
`25`		`-> * https://hdiconfigactions.blob.core.windows.net`
	`24`	`+> * http://security.ubuntu.com/ubuntu`
`26`	`25`
`27`	`26`	`## Preparation`
`28`	`27`