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

Author: craigshoemaker

articles/ai-services/openai/reference.md

@@ -1013,6 +1013,7 @@ POST https://{your-resource-name}.openai.azure.com/openai/deployments/{deploymen
 | `quality` | string | Optional | `standard` | The quality of the generated images. Must be `hd` or `standard`. |
 | `response_format` | string | Optional | `url` | The format in which the generated images are returned Must be `url` (a URL pointing to the image) or `b64_json` (the base 64-byte code in JSON format). |
 | `style` | string | Optional | `vivid` | The style of the generated images. Must be `natural` or `vivid` (for hyper-realistic / dramatic images). |
+| `user` | string | Optional || A unique identifier representing your end-user, which can help to monitor and detect abuse. |
 
 
 #### Example request

articles/ai-services/openai/whisper-quickstart.md

@@ -24,7 +24,7 @@ The file size limit for the Azure OpenAI Whisper model is 25 MB. If you need to
 
 - An Azure subscription - [Create one for free](https://azure.microsoft.com/free/cognitive-services?azure-portal=true).
 - Access granted to Azure OpenAI Service in the desired Azure subscription.
-- An Azure OpenAI resource created in the North Central US or West Europe regions with the `whisper` model deployed. For more information, see [Create a resource and deploy a model with Azure OpenAI](how-to/create-resource.md).
+- An Azure OpenAI resource with a `whisper` model deployed in a supported region. [Whisper model regional availability](./concepts/models.md#whisper-models). For more information, see [Create a resource and deploy a model with Azure OpenAI](how-to/create-resource.md).
 
 > [!NOTE]
 > Currently, you must submit an application to access Azure OpenAI Service. To apply for access, complete [this form](https://aka.ms/oai/access). 

articles/ai-studio/how-to/costs-plan-manage.md

@@ -63,12 +63,15 @@ Before you delete an Azure AI hub resource in the Azure portal or with Azure CLI
 - Azure AI Search (for the data)
 - Virtual machines
 - Load Balancer
-- Virtual Network
+- Azure Virtual Network
 - Bandwidth
 
 Each VM is billed per hour it's running. Cost depends on VM specifications. VMs that are running but not actively working on a dataset will still be charged via the load balancer. For each compute instance, one load balancer is billed per day. Every 50 nodes of a compute cluster have one standard load balancer billed. Each load balancer is billed around $0.33/day. To avoid load balancer costs on stopped compute instances and compute clusters, delete the compute resource.
 
-Compute instances also incur P10 disk costs even in stopped state. This is because any user content saved there's persisted across the stopped state similar to Azure VMs. We're working on making the OS disk size/ type configurable to better control costs. For virtual networks, one virtual network is billed per subscription and per region. Virtual networks can't span regions or subscriptions. Setting up private endpoints in virtual network setups might also incur charges. Bandwidth is charged by usage; the more data transferred, the more you're charged.
+Compute instances also incur P10 disk costs even in stopped state. This is because any user content saved there's persisted across the stopped state similar to Azure VMs. We're working on making the OS disk size/ type configurable to better control costs. For Azure Virtual Networks, one virtual network is billed per subscription and per region. Virtual networks can't span regions or subscriptions. Setting up private endpoints in virtual network setups might also incur charges. If your virtual network uses an Azure Firewall, this might also incur charges. Bandwidth is charged by usage; the more data transferred, the more you're charged. 
+
+> [!TIP]
+> Using an managed virtual network is free. However some features of the managed network rely on Azure Private Link (for private endpoints) and Azure Firewall (for FQDN rules) and will incur charges. For more information, see [Managed virtual network isolation](configure-managed-network.md#pricing).
 
 ### Costs might accrue after resource deletion
 

articles/aks/ingress-tls.md

@@ -7,7 +7,7 @@ ms.custom: devx-track-azurecli, devx-track-azurepowershell, linux-related-conten
 author: asudbring
 ms.author: allensu
 ms.topic: how-to
-ms.date: 12/13/2023
+ms.date: 03/14/2024
 ROBOTS: NOINDEX
 #Customer intent: As a cluster operator or developer, I want to use TLS with an ingress controller to handle the flow of incoming traffic and secure my apps using my own certificates or automatically generated certificates.
 ---
@@ -73,6 +73,9 @@ To use TLS with [Let's Encrypt][lets-encrypt] certificates, you'll deploy [cert-
 
 * Use `Import-AzContainerRegistryImage` to import the following images into your ACR.
 
+   >[!NOTE]
+   >When performing the steps to import the images into your ACR when working in Azure Government, you need to include the [`targetTag`][parameter-targettag] parameter with the value representing the tag of the image you want to import. 
+
     ```azurepowershell
     $RegistryName = "<REGISTRY_NAME>"
     $ResourceGroup = (Get-AzContainerRegistry | Where-Object {$_.name -eq $RegistryName} ).ResourceGroupName
@@ -659,4 +662,5 @@ You can also:
 [acr-helm]: ../container-registry/container-registry-helm-repos.md
 [get-az-aks-cluster]: /powershell/module/az.aks/get-azakscluster
 [new-az-public-ip-address]: /powershell/module/az.network/new-azpublicipaddress
-[aks-app-add-on]: app-routing.md
+[aks-app-add-on]: app-routing.md
+[parameter-targettag]: /powershell/module/az.containerregistry/import-azcontainerregistryimage

articles/app-service/manage-custom-dns-buy-domain.md

@@ -17,6 +17,11 @@ App Service domains are custom domains that are managed directly in Azure. They
 * To use an App Service domain, the app's [App Service plan](overview-hosting-plans.md) must be a paid tier and not **Free (F1)**. See [Scale up an app](manage-scale-up.md#scale-up-your-pricing-tier) to update the tier.
 * [Remove the spending limit on your subscription](../cost-management-billing/manage/spending-limit.md#remove).
 
+> [!NOTE]
+> Some subscriptions types would be required to have sufficient history on Azure prior to creating an App Service Domain.
+> Free trial and credit based subscriptions are not eligible to create an App Service Domain.
+>
+
 ## Buy and map an App Service domain
 
 For pricing information on App Service domains, visit the [App Service Pricing page](https://azure.microsoft.com/pricing/details/app-service/windows/) and scroll down to App Service Domain.
@@ -71,7 +76,6 @@ For pricing information on App Service domains, visit the [App Service Pricing p
     > [!NOTE]
     > App Service Domains use GoDaddy for domain registration and Azure DNS to host the domains. In addition to the yearly domain registration fee, usage charges for Azure DNS apply. For information, see [Azure DNS Pricing](https://azure.microsoft.com/pricing/details/dns/).
     >
-    >
 
 1. When the domain registration is complete, you see a **Go to resource** button. Select it to see its management page.
 
@@ -80,7 +84,9 @@ For pricing information on App Service domains, visit the [App Service Pricing p
 You're now ready to assign an App Service app to this custom domain.
 
 > [!NOTE]
-> Depending on the subscription type, a sufficient payment history within Azure may be required prior to creating an App Service domain. 
+> Some subscriptions types would be required to have sufficient history on Azure prior to creating an App Service Domain.
+> Free trial and credit based subscriptions are not eligible to create an App Service Domain.
+>
 
 ## Map a hostname manually
 

articles/azure-arc/servers/run-command.md

@@ -180,7 +180,14 @@ New-AzMachineRunCommand -ResourceGroupName MyRG0 -MachineName MyMachine -RunComm
 
 > [!NOTE]
 > SAS URL must provide read access to the blob. An expiry time of 24 hours is suggested for SAS URL. SAS URLs can be generated on Azure portal using blob options or SAS token using `New-AzStorageBlobSASToken`. If generating SAS token using `New-AzStorageBlobSASToken`, the SAS URL format is: base blob URL + "?" + the SAS token from `New-AzStorageBlobSASToken`.
-> 
+
+
+### Create or update Run Command on a machine using ScriptLocalPath (local script file)
+Create or update Run Command on a machine using a local script file that is on the client machine where cmdlet is executed.
+
+```powershell
+New-AzMachineRunCommand -ResourceGroupName MyRG0 -VMName MyMachine -RunCommandName MyRunCommand -Location EastUS2EUAP -ScriptLocalPath "C:\MyScriptsDir\MyScript.ps1"
+```
 
 ### Create or update Run Command on a machine instance using Parameter and ProtectedParameter parameters (Public and Protected Parameters to script)
 
@@ -224,19 +231,21 @@ Start off by creating a Run Command script to provide endpoint access to the `ww
 
 To directly provide the script in line, use the following operation:
 
-```
+```rest
 PUT https://management.azure.com/subscriptions/aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa/resourceGroups/ContosoRG/providers/Microsoft.HybridCompute/machines/2012DatacenterServer1/runCommands/EndpointAccessCommand?api-version=2023-10-03-preview
+```
 
+```json
 {
   "location": "eastus2",
   "properties": {
     "source": {
-      "script": " New-NetFirewallRule -DisplayName $ruleName -Direction Outbound -Action Allow -RemoteAddress $endpoint -RemotePort $port -Protocol $protocol”
+      "script": "New-NetFirewallRule -DisplayName $ruleName -Direction Outbound -Action Allow -RemoteAddress $endpoint -RemotePort $port -Protocol $protocol"
     },
     "parameters": [
       {
         "name": "ruleName",
-        "value": " Allow access to www.microsoft.com/pkiops/certs"
+        "value": "Allow access to www.microsoft.com/pkiops/certs"
       },
       {
         "name": "endpoint",
@@ -254,7 +263,7 @@ PUT https://management.azure.com/subscriptions/aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaa
     ],
     "asyncExecution": false,
     "runAsUser": "contoso-user1",
-    "runAsPassword": "Contoso123!”
+    "runAsPassword": "Contoso123!"
     "timeoutInSeconds": 3600,
     "outputBlobUri": "https://mystorageaccount.blob.core.windows.net/myscriptoutputcontainer/MyScriptoutput.txt",
     "errorBlobUri": "https://mystorageaccount.blob.core.windows.net/mycontainer/MyScriptError.txt"
@@ -264,9 +273,11 @@ PUT https://management.azure.com/subscriptions/aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaa
 
 To instead link to the script file, you can use the Run Command operation’s ScriptURI option. For this it's assumed you have prepared a `newnetfirewallrule.ps1` file containing the in-line script and uploaded this script to blob storage.
 
-```
+```rest
 PUT https://management.azure.com/subscriptions/aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa/resourceGroups/ContosoRG/providers/Microsoft.HybridCompute/machines/2012DatacenterServer1/runCommands/EndpointAccessCommand?api-version=2023-10-03-preview
+```
 
+```json
 {
   "location": "eastus2",
   "properties": {
@@ -294,7 +305,7 @@ PUT https://management.azure.com/subscriptions/aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaa
     ],
     "asyncExecution": false,
     "runAsUser": "contoso-user1",
-    "runAsPassword": "Contoso123!”
+    "runAsPassword": "Contoso123!"
     "timeoutInSeconds": 3600,
     "outputBlobUri": "https://mystorageaccount.blob.core.windows.net/myscriptoutputcontainer/MyScriptoutput.txt",
     "errorBlobUri": "https://mystorageaccount.blob.core.windows.net/mycontainer/MyScriptError.txt"
@@ -304,13 +315,13 @@ PUT https://management.azure.com/subscriptions/aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaa
 
 SAS URL must provide read access to the blob. An expiry time of 24 hours is suggested for SAS URL. SAS URLs can be generated on Azure portal using blobs options or SAS token using `New-AzStorageBlobSASToken`. If generating SAS token using `New-AzStorageBlobSASToken`, the SAS URL format is: `base blob URL + "?"` + the SAS token from `New-AzStorageBlobSASToken`. 
 
-Output and error blobs must be the AppendBlob type and their SAS URLs must provide read, append, create, write access to the blob. An expiration time of 24 hours is suggested for SAS URL. SAS URLs can be generated on Azure portal using blob's options, or SAS token from using New-`AzStorageBlobSASToken`.
+Output and error blobs must be the AppendBlob type and their SAS URLs must provide read, append, create, write access to the blob. An expiration time of 24 hours is suggested for SAS URL. SAS URLs can be generated on Azure portal using blob's options, or SAS token from using `New-AzStorageBlobSASToken`.
 
 ### Example 2: Get Run Command details
 
 To verify that you've correctly provisioned the Run Command, use the GET command to retrieve details on the provisioned Run Command:
 
-```
+```rest
 GET https://management.azure.com/subscriptions/aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa/resourceGroups/ContosoRG/providers/Microsoft.HybridCompute/machines/2012DatacenterServer1/runCommands/EndpointAccessCommand?api-version=2023-10-03-preview
 ```
 
@@ -319,23 +330,25 @@ GET https://management.azure.com/subscriptions/aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaa
 Let’s suppose you want to open up access to an additional endpoint `*.waconazure.com` for connectivity to Windows Admin Center. You can update the existing Run Command with new parameters:
 
 
-```
+```rest
 PATCH https://management.azure.com/subscriptions/aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa/resourceGroups/ContosoRG/providers/Microsoft.HybridCompute/machines/2012DatacenterServer1/runCommands/EndpointAccessCommand?api-version=2023-10-03-preview
+```
 
+```json
 {
   "location": "eastus2",
   "properties": {
     "source": {
-      "script": " New-NetFirewallRule -DisplayName $ruleName -Direction Outbound -Action Allow -RemoteAddress $endpoint -RemotePort $port -Protocol $protocol”
+      "script": "New-NetFirewallRule -DisplayName $ruleName -Direction Outbound -Action Allow -RemoteAddress $endpoint -RemotePort $port -Protocol $protocol"
     },
     "parameters": [
       {
         "name": "ruleName",
-        "value": " Allow access to WAC endpoint"
+        "value": "Allow access to WAC endpoint"
       },
       {
         "name": "endpoint",
-        "value": “*.waconazure.com”
+        "value": "*.waconazure.com"
       },
       {
         "name": "port",
@@ -361,15 +374,15 @@ PATCH https://management.azure.com/subscriptions/aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaa
 
 Ahead of deleting the Run Command for Endpoint Access, make sure there are no other Run Commands for the Arc-enabled server. You can use the list command to get all of the Run Commands:
 
-```
+```rest
 LIST https://management.azure.com/subscriptions/aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa/resourceGroups/ContosoRG/providers/Microsoft.HybridCompute/machines/2012DatacenterServer1/runCommands/
 ```
 
 ### Example 5: Delete a Run Command
 
 If you no longer need the Run Command extension, you can delete it using the following command:
 
-```
+```rest
 DELETE https://management.azure.com/subscriptions/ aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa/resourceGroups/ContosoRG/providers/Microsoft.HybridCompute/machines/2012DatacenterServer1/runCommands/EndpointAccessCommand?api-version=2023-10-03-preview
 ```
 

articles/azure-functions/durable/durable-functions-dotnet-isolated-overview.md

@@ -61,7 +61,7 @@ public class MyActivity : TaskActivity<string, string>
 {
     private readonly ILogger logger;
 
-    public MyActivity(ILogger<SayHelloTyped> logger) // activites have access to DI.
+    public MyActivity(ILogger<MyActivity> logger) // activites have access to DI.
     {
         this.logger = logger;
     }

articles/azure-functions/functions-bindings-azure-sql-trigger.md

@@ -219,9 +219,9 @@ public class SqlChangeToDoItem {
     public SqlChangeToDoItem() {
     }
 
-    public SqlChangeToDoItem(ToDoItem item, SqlChangeOperation operation) {
-        this.item = item;
-        this.operation = operation;
+    public SqlChangeToDoItem(ToDoItem Item, SqlChangeOperation Operation) {
+        this.Item = Item;
+        this.Operation = Operation;
     }
 }
 ```

articles/azure-functions/functions-bindings-cosmosdb-v2-output.md

@@ -37,7 +37,7 @@ This article supports both programming models.
 ::: zone-end
 ## Example
 
-Unless otherwise noted, examples in this article target version 3.x of the [Azure Cosmos DB extension](functions-bindings-cosmosdb-v2.md). For use with extension version 4.x, you need to replace the string `collection` in property and attribute names with `container`.
+Unless otherwise noted, examples in this article target version 3.x of the [Azure Cosmos DB extension](functions-bindings-cosmosdb-v2.md). For use with extension version 4.x, you need to replace the string `collection` in property and attribute names with `container` and `connection_string_setting` with `connection`.
 
 ::: zone pivot="programming-language-csharp"
 

articles/azure-monitor/app/standard-metrics.md

@@ -9,7 +9,7 @@ ms.reviewer: vitalyg
 
 # Application Insights standard metrics
 
-Standard metrics are pre-aggregated during collection, they have better performance at query time. This makes them the best choice for dashboards and real-time alerting.
+Standard metrics are pre-aggregated during collection, which gives them better performance at query time. This makes them the best choice for dashboards and real-time alerting.
 
 [!INCLUDE [azure-monitor-app-insights-otel-available-notification](../includes/azure-monitor-app-insights-otel-available-notification.md)]