Merge pull request #265814 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: v-alje

articles/ai-services/openai/how-to/assistant.md

@@ -373,14 +373,6 @@ print(image_file_id)  # Outputs: assistant-1YGVTvNzc2JXajI5JU9F0HMD
 ### Download image
 
 ```python
-from openai import AzureOpenAI
-    
-client = AzureOpenAI(
-    api_key=os.getenv("AZURE_OPENAI_KEY"),  
-    api_version="2024-02-15-preview",
-    azure_endpoint = os.getenv("AZURE_OPENAI_ENDPOINT")
-    )
-
 content = client.files.content(image_file_id)
 
 image= content.write_to_file("sinewave.png")

articles/azure-arc/resource-bridge/upgrade.md

@@ -64,7 +64,7 @@ Arc resource bridge can be manually upgraded from the management machine. You mu
 
 Manual upgrade generally takes between 30-90 minutes, depending on network speeds. The upgrade command takes your Arc resource bridge to the next appliance version, which might not be the latest available appliance version. Multiple upgrades could be needed to reach a [supported version](#supported-versions). You can check your appliance version by checking the Azure resource of your Arc resource bridge.
 
-To manually upgrade your Arc resource bridge, make sure you're using the latest `az arcappliance` CLI extension by running the extension upgrade command from the management machine:
+Before upgrading, you'll need the latest Azure CLI extension for `arcappliance`:
 
 ```azurecli
 az extension add --upgrade --name arcappliance 
@@ -78,7 +78,7 @@ az arcappliance upgrade <private cloud> --config-file <file path to ARBname-appl
 
 For example, to upgrade a resource bridge on VMware, run: `az arcappliance upgrade vmware --config-file c:\contosoARB01-appliance.yaml`
 
-To upgrade a resource bridge on System Center Virtual Machine Manager (SCVMM), run: `az arcappliance upgrade scvmm --config-file c:\contosoARB01-appliance.yaml`
+To upgrade a resource bridge on SCVMM, run: `az arcappliance upgrade scvmm --config-file c:\contosoARB01-appliance.yaml`
 
 To upgrade a resource bridge on Azure Stack HCI, please transition to 23H2 and use the built-in upgrade management tool. More info available [here](/azure-stack/hci/update/about-updates-23h2).
 

articles/communication-services/concepts/telephony/direct-routing-sip-specification.md

@@ -150,11 +150,11 @@ Call context headers are currently available only for Call Automation SDK. Call
 
 ### User-To-User header
 
-SIP User-To-User (UUI) header is an industry standard to pass contextual information during a call setup process. The maximum length of a UUI header key is 64 chars. The maximum length of UUI header value is 256 chars.
+SIP User-To-User (UUI) header is an industry standard to pass contextual information during a call setup process. The maximum length of a UUI header key is 64 chars. The maximum length of UUI header value is 256 chars. The UUI header value might consist of alphanumeric characters and a few selected symbols, including "=", ";", ".", "!", "%", "*", "_", "+", "~", "-".
 
 ### Custom header
 
-Azure Communication Services also supports up to five custom SIP headers. Custom SIP header key must start with a mandatory `X-MS-Custom-` prefix. The maximum length of a SIP header key is 64 chars, including the `X-MS-Custom-` prefix. The maximum length of SIP header value is 256 chars. 
+Azure Communication Services also supports up to five custom SIP headers. Custom SIP header key must start with a mandatory `X-MS-Custom-` prefix. The maximum length of a SIP header key is 64 chars, including the `X-MS-Custom-` prefix. The SIP header key might consist of alphanumeric characters and a few selected symbols, including ".", "!", "%", "*", "_", "+", "~", "-". The maximum length of the SIP header value is 256 characters. The SIP header value might consist of alphanumeric characters and a few selected symbols, including "=", ";", ".", "!", "%", "*", "_", "+", "~", "-".
 
 For implementation details refer to [How to pass contextual data between calls](../../how-tos/call-automation/custom-context.md).
 

articles/virtual-network/accelerated-networking-overview.md

@@ -1,12 +1,12 @@
 ---
 title: Accelerated Networking overview
 description: Learn how Accelerated Networking can improve the networking performance of Azure VMs.
-author: steveesp
+author: EllieMelissa
 ms.service: virtual-network
 ms.custom: linux-related-content
 ms.topic: how-to
 ms.date: 04/18/2023
-ms.author: steveesp
+ms.author: ealume
 ---
 
 # Accelerated Networking overview
@@ -44,6 +44,8 @@ Accelerated Networking has the following benefits:
 
 - You can't deploy virtual machines (classic) with Accelerated Networking through Azure Resource Manager.
 
+- The Azure platform does not update the Mellanox NIC drivers in the VM. For VMs running Linux and FreeBSD, customers are encouraged to stay current with the latest kernel updates offered by the distribution. For VMs running Windows, customers should apply updated drivers from the Nvidia support page if any issues are later encountered with the driver delivered with the Marketplace image or applied to a custom image.
+
 ### Supported regions
 
 Accelerated Networking is available in all global Azure regions and the Azure Government Cloud.

articles/virtual-network/create-vm-accelerated-networking-cli.md

@@ -250,6 +250,25 @@ For more information about application binding requirements, see [How Accelerate
 
 <a name="enable-accelerated-networking-on-existing-vms"></a>
 
+In order to ensure that your custom image or applications correctly support the dynamic binding and revocation of virtual functions, the functionality can be tested on any Windows Hyper-V server. Use a local Windows Server running Hyper-V in the following configuration:
+ - Ensure you have a physical network adapter that supports SR-IOV.
+ - An external virtual switch is created on top of this SR-IOV adapter with "Enable single-root I/O virtualization (SR-IOV)" checked.
+ - A virtual machine running your operating system image or application is created/deployed.
+ - The network adapters for this virtual machine, under Hardware Acceleration, have "Enable SR-IOV" selected.
+
+Once you've verified your virtual machine and application are leveraging a network adapter using SR-IOV, you can modify the following example commands to toggle SR-IOV off/on in order to revoke and add the virtual function which will simulate what happens during Azure host servicing:
+
+``` Powershell
+# Get the virtual network adapter to test
+$vmNic = Get-VMNetworkAdapter -VMName "myvm" | where {$_.MacAddress -eq "001122334455"}
+
+# Enable SR-IOV on a virtual network adapter
+Set-VMNetworkAdapter $vmNic -IovWeight 100 -IovQueuePairsRequested 1
+
+# Disable SR-IOV on a virtual network adapter
+Set-VMNetworkAdapter $vmNic -IovWeight 0
+```
+
 ## Manage Accelerated Networking on existing VMs
 
 It's possible to enable Accelerated Networking on an existing VM. The VM must meet the following requirements to support Accelerated Networking: