Merge pull request #269076 from MicrosoftDocs/main

3/14/2024 AM Publish

Author: Taojunshen

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/faq.yml

@@ -6,7 +6,7 @@ metadata:
   manager: nitinme
   ms.service: azure-ai-studio
   ms.topic: faq
-  ms.date: 2/6/2024
+  ms.date: 3/14/2024
   ms.reviewer: eur
   ms.author: eur
   author: eric-urban
@@ -40,10 +40,6 @@ sections:
           How is the playground in Azure AI Studio different from the Azure OpenAI Studio playground? 
         answer: |
           The playground experiences in both Azure AI Studio and Azure OpenAI Studio are similar; however, Azure AI Studio provides playground experience for models in addition to those provisioned via Azure OpenAI Studio.
-      - question: |
-          What is the plan for plugin support? 
-        answer: |
-          Plugins are available today in preview. For more information, see [Plugins for Azure OpenAI Service - Microsoft Community Hub](https://techcommunity.microsoft.com/t5/microsoft-azure-netherlands/how-to-leverage-plugins-for-azure-openai-service/m-p/3863986).
       - question: |
           Will there be multiple varying model benchmarks in Azure AI Studio based on individual projects and data sources? 
         answer: |

articles/app-service/environment/how-to-custom-domain-suffix.md

@@ -27,6 +27,8 @@ If the certificate used for the custom domain suffix contains a Subject Alternat
 
 Unlike earlier versions, the FTPS endpoints for your App Services on your App Service Environment v3 can only be reached using the default domain suffix.
 
+The connection to the custom domain suffix endpoint will need to use Server Name Indication (SNI) for TLS based connections.
+
 ## Prerequisites
 
 - ILB variation of App Service Environment v3.

articles/app-service/environment/version-comparison.md

@@ -64,7 +64,7 @@ App Service Environment v3 runs on the latest [Virtual Machine Scale Sets](../..
 |Feature  |[App Service Environment v1](app-service-app-service-environment-intro.md)  |[App Service Environment v2](intro.md)  |[App Service Environment v3](overview.md)  |
 |---------|---------|---------|---------|
 |IP-based Transport Layer Security (TLS) or Secure Sockets Layer (SSL) binding with your apps     |Yes         |Yes         |No         |
-|Custom domain suffix    |Yes         |Yes (only supported with certain API versions)         |[Yes](how-to-custom-domain-suffix.md)         |
+|Custom domain suffix    |Yes (requires SNI based TLS connection)        |Yes (only supported with certain API versions)         |[Yes](how-to-custom-domain-suffix.md)         |
 |Support for App Service Managed Certificates   |No         |No         |No        |
 
 ### Backup and restore

articles/app-service/overview-vnet-integration.md

@@ -68,7 +68,7 @@ For Windows App Service plans, the virtual network integration feature supports
 
 Virtual network integration depends on a dedicated subnet. When you create a subnet, the Azure subnet consumes five IPs from the start. One address is used from the integration subnet for each App Service plan instance. If you scale your app to four instances, then four addresses are used.
 
-When you scale up/down in size or in/out in number of instances, the required address space is doubled for a short period of time. The scale operation adds the same number of new instances and then deletes the existing instances. The scale operation affects the real, available supported instances for a given subnet size. Platform upgrades need free IP addresses to ensure upgrades can happen without interruptions to outbound traffic. Finally, after scale up, down, or in operations complete, there might be a short period of time before IP addresses are released. 
+When you scale up/down in instance size, the amount of IP addresses used by the App Service plan is temporarily doubled while the scale operation completes. The new instances need to be fully operational before the existing instances are deprovisioned. The scale operation affects the real, available supported instances for a given subnet size. Platform upgrades need free IP addresses to ensure upgrades can happen without interruptions to outbound traffic. Finally, after scale up, down, or in operations complete, there might be a short period of time before IP addresses are released. In rare cases, this operation can be up to 12 hours.
 
 Because subnet size can't be changed after assignment, use a subnet that's large enough to accommodate whatever scale your app might reach. You should also reserve IP addresses for platform upgrades. To avoid any issues with subnet capacity, use a `/26` with 64 addresses. When you're creating subnets in Azure portal as part of integrating with the virtual network, a minimum size of /27 is required. If the subnet already exists before integrating through the portal, you can use a /28 subnet.
 
@@ -197,7 +197,7 @@ There are some limitations with using virtual network integration:
 * The integration subnet can't have [service endpoint policies](../virtual-network/virtual-network-service-endpoint-policies-overview.md) enabled.
 * Only one App Service plan virtual network integration connection per integration subnet is supported.
 * You can't delete a virtual network with an integrated app. Remove the integration before you delete the virtual network.
-* You can't have more than two virtual network integrations per Windows App Service plan. You can't have more than one virtual network integration per Linux App Service plan. Multiple apps in the same App Service plan can use the same virtual network integration.
+* You can't have more than two virtual network integrations per App Service plan. Multiple apps in the same App Service plan can use the same virtual network integration.
 * You can't change the subscription of an app or a plan while there's an app that's using virtual network integration.
 
 ## Access on-premises resources

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-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)]
 

articles/communication-services/concepts/call-automation/play-action.md

@@ -49,7 +49,7 @@ As part of compliance requirements in various industries, vendors are expected t
 
 ## Known limitations
 - Text-to-Speech text prompts support a maximum of 400 characters, if your prompt is longer than this we suggest using SSML for Text-to-Speech based play actions.
-- For scenarios where you exceed your Speech service quota limit, you can request to increase this lilmit by following the steps outlined [here](../../../ai-services/speech-service/speech-services-quotas-and-limits.md).
+- For scenarios where you exceed your Speech service quota limit, you can request to increase this limit by following the steps outlined [here](../../../ai-services/speech-service/speech-services-quotas-and-limits.md).
 
 ## Next Steps
 - Check out our how-to guide to learn [how-to play custom voice prompts](../../how-tos/call-automation/play-action.md) to users.