Merge pull request #271884 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: Taojunshen

articles/azure-monitor/app/availability-overview.md

@@ -15,6 +15,7 @@ You can set up availability tests for any HTTP or HTTPS endpoint that's accessib
 ## Types of tests
 
 > [!IMPORTANT]
+> There are two upcoming availability tests retirements. On August 31, 2024 multi-step web tests in Application Insights will be retired. We advise users of these tests to transition to alternative availability tests before the retirement date. Following this date, we will be taking down the underlying infrastructure which will break remaining multi-step tests.
 > On September 30, 2026, URL ping tests in Application Insights will be retired. Existing URL ping tests will be removed from your resources. Review the [pricing](https://azure.microsoft.com/pricing/details/monitor/#pricing) for standard tests and [transition](https://aka.ms/availabilitytestmigration) to using them before September 30, 2026 to ensure you can continue to run single-step availability tests in your Application Insights resources.
 
 There are four types of availability tests:
@@ -56,4 +57,4 @@ Our [web tests](/previous-versions/azure/azure-monitor/app/monitor-web-app-avail
 * [Availability alerts](availability-alerts.md)
 * [Standard tests](availability-standard-tests.md)
 * [Create and run custom availability tests using Azure Functions](availability-azure-functions.md)
-* [Web tests Azure Resource Manager template](/azure/templates/microsoft.insights/webtests?tabs=json)
+* [Web tests Azure Resource Manager template](/azure/templates/microsoft.insights/webtests?tabs=json)

articles/azure-vmware/configure-pure-cloud-block-store.md

@@ -20,8 +20,8 @@ Pure Storage manages onboarding of Pure Cloud Block Store for Azure VMware Solut
 
 For more information, see the following resources: 
 
-- [Azure VMware Solution + CBS Implementation Guide](https://support.purestorage.com/Pure_Cloud_Block_Store/Azure_VMware_Solution_and_Cloud_Block_Store_Implementation_Guide)
-- [CBS Deployment Guide](https://support.purestorage.com/Pure_Cloud_Block_Store/Pure_Cloud_Block_Store_on_Azure_Implementation_Guide)
+- [Azure VMware Solution + CBS Implementation Guide](https://support.purestorage.com/bundle/m_cbs_for_azure_vmware_solution/page/production-branch/content/documents/Production/Pure_Cloud_Block_Store/topics/concept/c_azure_vmware_solution_and_cloud_block_store_implementation_g.html)
+- [CBS Deployment Guide](https://support.purestorage.com/bundle/m_cbs_for_azure_vmware_solution/page/production-branch/content/documents/Production/Pure_Cloud_Block_Store/topics/concept/c_azure_vmware_solution_and_cloud_block_store_implementation_g.html)
 - [CBS Deployment Troubleshooting](https://support.purestorage.com/Pure_Cloud_Block_Store/Pure_Cloud_Block_Store_on_Azure_-_Troubleshooting_Guide)
 - [CBS support articles](https://support.purestorage.com/Pure_Cloud_Block_Store/CBS_on_Azure_VMware_Solution_Troubleshooting_Article_Index)
 - [Videos](https://support.purestorage.com/Pure_Cloud_Block_Store/Azure_VMware_Solution_and_Cloud_Block_Store_Video_Demos)

articles/azure-web-pubsub/quickstart-serverless.md

@@ -63,6 +63,16 @@ In this tutorial, you learn how to:
 
 - The [Azure CLI](/cli/azure) to manage Azure resources.
 
+# [Python](#tab/python)
+
+- A code editor, such as [Visual Studio Code](https://code.visualstudio.com/).
+
+- [Python](https://www.python.org/downloads/) (v3.7+). See [supported Python versions](../azure-functions/functions-reference-python.md#python-version).
+
+- [Azure Functions Core Tools](https://github.com/Azure/azure-functions-core-tools#installing) (v4 or higher preferred) to run Azure Function apps locally and deploy to Azure.
+
+- The [Azure CLI](/cli/azure) to manage Azure resources.
+
 ---
 
 [!INCLUDE [quickstarts-free-trial-note](../../includes/quickstarts-free-trial-note.md)]
@@ -97,6 +107,12 @@ In this tutorial, you learn how to:
    func init --worker-runtime dotnet-isolated
    ```
 
+   # [Python](#tab/python)
+
+   ```bash
+   func init --worker-runtime python --model V1
+   ```
+
 2. Install `Microsoft.Azure.WebJobs.Extensions.WebPubSub`.
 
    # [JavaScript Model v4](#tab/javascript-v4)
@@ -137,6 +153,17 @@ In this tutorial, you learn how to:
    dotnet add package Microsoft.Azure.Functions.Worker.Extensions.WebPubSub --prerelease
    ```
 
+   # [Python](#tab/python)
+
+   ```json
+   {
+     "extensionBundle": {
+       "id": "Microsoft.Azure.Functions.ExtensionBundle",
+       "version": "[3.3.*, 4.0.0)"
+   }
+   ```
+   
+
 3. Create an `index` function to read and host a static web page for clients.
 
    ```bash
@@ -254,6 +281,45 @@ In this tutorial, you learn how to:
      }
      ```
 
+   # [Python](#tab/python)
+
+   - Update `index/function.json` and copy following json codes.
+   
+     ```json
+     {
+       "bindings": [
+         {
+           "authLevel": "anonymous",
+           "type": "httpTrigger",
+           "direction": "in",
+           "name": "req",
+           "methods": ["get", "post"]
+         },
+         {
+           "type": "http",
+           "direction": "out",
+           "name": "$return"
+         }
+       ]
+     }
+
+     ```
+     
+
+   - Update `__init__.py` and replace `main` function with following codes.
+   
+     ```python
+     import os
+
+     import azure.functions as func
+
+
+     def main(req: func.HttpRequest) -> func.HttpResponse:
+         f = open(os.path.dirname(os.path.realpath(__file__)) + "/../index.html")
+         return func.HttpResponse(f.read(), mimetype="text/html")
+     ```
+     
+
 4. Create a `negotiate` function to help clients get service connection url with access token.
 
    ```bash
@@ -354,6 +420,46 @@ In this tutorial, you learn how to:
      }
      ```
 
+   # [Python](#tab/python)
+
+   - Update `negotiate/function.json` and copy following json codes. 
+     ```json
+     {
+       "bindings": [
+         {
+           "authLevel": "anonymous",
+           "type": "httpTrigger",
+           "direction": "in",
+           "name": "req"
+         },
+         {
+           "type": "http",
+           "direction": "out",
+           "name": "$return"
+         },
+         {
+           "type": "webPubSubConnection",
+           "name": "connection",
+           "hub": "simplechat",
+           "userId": "{headers.x-ms-client-principal-name}",
+           "direction": "in"
+         }
+       ]
+     }
+     ```
+
+   - Update `negotiate/__init__.py` and copy following codes.
+     ```python
+     import azure.functions as func
+
+
+     def main(req: func.HttpRequest, connection) -> func.HttpResponse:
+         return func.HttpResponse(connection)
+
+     ```
+     
+     
+
 5. Create a `message` function to broadcast client messages through service.
 
    ```bash
@@ -483,6 +589,50 @@ In this tutorial, you learn how to:
      }
      ```
 
+   # [Python](#tab/python)
+
+   - Update `message/function.json` and copy following json codes.
+     ```json
+     {
+       "bindings": [
+         {
+           "type": "webPubSubTrigger",
+           "direction": "in",
+           "name": "request",
+           "hub": "simplechat",
+           "eventName": "message",
+           "eventType": "user"
+         },
+         {
+           "type": "webPubSub",
+           "name": "actions",
+           "hub": "simplechat",
+           "direction": "out"
+         }
+       ]
+     }
+     ``` 
+   - Update `message/__init__.py` and copy following codes.
+     ```python
+     import json
+
+     import azure.functions as func
+     
+     
+     def main(request, actions: func.Out[str]) -> None:
+         req_json = json.loads(request)
+         actions.set(
+             json.dumps(
+                 {
+                     "actionName": "sendToAll",
+                     "data": f'[{req_json["connectionContext"]["userId"]}] {req_json["data"]}',
+                     "dataType": req_json["dataType"],
+                 }
+             )
+         )
+     ```
+     
+
 6. Add the client single page `index.html` in the project root folder and copy content.
 
    ```html
@@ -561,6 +711,8 @@ In this tutorial, you learn how to:
    </ItemGroup>
    ```
 
+   # [Python](#tab/python)
+
 ## Create and Deploy the Azure Function App
 
 Before you can deploy your function code to Azure, you need to create three resources:
@@ -621,6 +773,12 @@ Use the following commands to create these items.
    az functionapp create --resource-group WebPubSubFunction --consumption-plan-location <REGION> --runtime dotnet-isolated --functions-version 4 --name <FUNCIONAPP_NAME> --storage-account <STORAGE_NAME>
    ```
 
+   # [Python](#tab/python)
+
+   ```azurecli
+   az functionapp create --resource-group WebPubSubFunction --consumption-plan-location <REGION> --runtime python --runtime-version 3.9 --functions-version 4 --name <FUNCIONAPP_NAME> --os-type linux --storage-account <STORAGE_NAME>
+   ```
+
 1. Deploy the function project to Azure:
 
    After you have successfully created your function app in Azure, you're now ready to deploy your local functions project by using the [func azure functionapp publish](./../azure-functions/functions-run-local.md) command.

articles/expressroute/how-to-configure-coexisting-gateway-portal.md

@@ -33,6 +33,7 @@ The steps to configure both scenarios are covered in this article. You can confi
 
 * **Only route-based VPN gateway is supported.** You must use a route-based [VPN gateway](../vpn-gateway/vpn-gateway-about-vpngateways.md). You also can use a route-based VPN gateway with a VPN connection configured for 'policy-based traffic selectors' as described in [Connect to multiple policy-based VPN devices](../vpn-gateway/vpn-gateway-connect-multiple-policybased-rm-ps.md).
 * **ExpressRoute-VPN Gateway coexist configurations are not supported on the Basic SKU**.
+* **Both the ExpressRoute and VPN gateways must be able to communicate with each other via BGP to function properly.** If using a UDR on the gateway subnet, ensure that it does not include a route for the gateway subnet rage itself as this will interfere with BGP traffic.
 * **If you want to use transit routing between ExpressRoute and VPN, the ASN of Azure VPN Gateway must be set to 65515.** Azure VPN Gateway supports the BGP routing protocol. For ExpressRoute and Azure VPN to work together, you must keep the Autonomous System Number of your Azure VPN gateway at its default value, 65515. If you previously selected an ASN other than 65515 and you change the setting to 65515, you must reset the VPN gateway for the setting to take effect.
 * **The gateway subnet must be /27 or a shorter prefix**, such as /26, /25, or you receive an error message when you add the ExpressRoute virtual network gateway.
 * **Coexistence for IPv4 traffic only.** ExpressRoute co-existence with VPN gateway is supported, but only for IPv4 traffic. IPv6 traffic isn't supported for VPN gateways.
@@ -131,4 +132,4 @@ You can add a Point-to-Site configuration to your coexisting set by following th
 If you want to enable connectivity between one of your local networks that is connected to ExpressRoute and another of your local network that is connected to a site-to-site VPN connection, you need to set up [Azure Route Server](../route-server/expressroute-vpn-support.md).
 
 ## Next steps
-For more information about ExpressRoute, see the [ExpressRoute FAQ](expressroute-faqs.md).
+For more information about ExpressRoute, see the [ExpressRoute FAQ](expressroute-faqs.md).

articles/healthcare-apis/dicom/dicom-services-conformance-statement-v2.md

@@ -58,12 +58,14 @@ The [Studies Service](https://dicom.nema.org/medical/dicom/current/output/html/p
 
 ### Store (STOW-RS)
 
-This transaction uses the POST method to store representations of studies, series, and instances contained in the request payload.
+This transaction uses the POST or PUT method to store representations of studies, series, and instances contained in the request payload.
 
 | Method | Path               | Description |
 | :----- | :----------------- | :---------- |
 | POST   | ../studies         | Store instances. |
 | POST   | ../studies/{study} | Store instances for a specific study. |
+| PUT    | ../studies         | Upsert instances. |
+| PUT    | ../studies/{study} | Upsert instances for a specific study. |
 
 Parameter `study` corresponds to the DICOM attribute StudyInstanceUID. If specified, any instance that doesn't belong to the provided study is rejected with a `43265` warning code.
 
@@ -77,7 +79,7 @@ The following `Content-Type` header(s) are supported:
 * `application/dicom`
 
 > [!NOTE]
-> The Server **will not** coerce or replace attributes that conflict with existing data. All data will be stored as provided.
+> The server won't coerce or replace attributes that conflict with existing data for POST requests. All data is stored as provided. For upsert (PUT) requests, the existing data is replaced by the new data received. 
 
 #### Store required attributes
 The following DICOM elements are required to be present in every DICOM file attempting to be stored:

articles/healthcare-apis/dicom/dicom-services-conformance-statement.md

@@ -58,12 +58,14 @@ The [Studies Service](https://dicom.nema.org/medical/dicom/current/output/html/p
 
 ### Store (STOW-RS)
 
-This transaction uses the POST method to store representations of studies, series, and instances contained in the request payload.
+This transaction uses the POST or PUT method to store representations of studies, series, and instances contained in the request payload.
 
 | Method | Path               | Description |
 | :----- | :----------------- | :---------- |
 | POST   | ../studies         | Store instances. |
 | POST   | ../studies/{study} | Store instances for a specific study. |
+| PUT    | ../studies         | Upsert instances. |
+| PUT    | ../studies/{study} | Upsert instances for a specific study. |
 
 Parameter `study` corresponds to the DICOM attribute StudyInstanceUID. If specified, any instance that doesn't belong to the provided study is rejected with a `43265` warning code.
 
@@ -77,7 +79,7 @@ The following `Content-Type` header(s) are supported:
 * `application/dicom`
 
 > [!NOTE]
-> The Server **will not** coerce or replace attributes that conflict with existing data. All data will be stored as provided.
+> The server won't coerce or replace attributes that conflict with existing data for POST requests. All data is stored as provided. For upsert (PUT) requests, the existing data is replaced by the new data received. 
 
 #### Store required attributes
 The following DICOM elements are required to be present in every DICOM file attempting to be stored: