Merge pull request #308134 from MicrosoftDocs/main

learn-build-service-prod[bot] · web-flow · commit e79d72f90c85 · 2025-11-11T06:11:14.000Z
Auto Publish – main to live - 2025-11-11 06:00 UTC
diff --git a/articles/backup/backup-azure-enhanced-soft-delete-configure-manage.md b/articles/backup/backup-azure-enhanced-soft-delete-configure-manage.md
@@ -24,7 +24,7 @@ This article describes how to configure and use [soft delete](secure-by-default.
 
 | Vault Type               | Availability Type    | Regions                                      |
 |--------------------------|----------------------|---------------------------------------------|
-| Recovery Services Vault  | General Availability | East Asia                                   |
+| Recovery Services Vault  | General Availability | West Central US                            |
 | Recovery Services Vault  | Preview              | All remaining Azure Public Regions         |
 | Backup Vault             | Preview              | Australia East, West Central US, East Asia |
 
diff --git a/articles/backup/secure-by-default.md b/articles/backup/secure-by-default.md
@@ -30,7 +30,7 @@ Secure by default with soft delete for Azure Backup allows you to recover your b
 
 | Vault Type               | Availability Type    | Regions                                      |
 |--------------------------|----------------------|---------------------------------------------|
-| Recovery Services Vault  | General Availability | East Asia                                   |
+| Recovery Services Vault  | General Availability | West Central US                            |
 | Recovery Services Vault  | Preview              | All remaining Azure Public Regions         |
 | Backup Vault             | Preview              | Australia East, West Central US, East Asia |
 
diff --git a/articles/backup/threat-detection-overview.md b/articles/backup/threat-detection-overview.md
@@ -8,6 +8,7 @@ ms.reviewer: v-mallicka
 ms.date: 11/10/2025
 ms.topic: tutorial
 ms.service: azure-backup
+ms.custom: references_regions
 ---
 
 # Threat Detection in Azure Backup with Microsoft Defender for Cloud integration (preview)
diff --git a/articles/communication-services/concepts/sms/media/message-connect-send-receive-sms.png b/articles/communication-services/concepts/sms/media/message-connect-send-receive-sms.png
diff --git a/articles/communication-services/concepts/sms/media/sms-concept.png b/articles/communication-services/concepts/sms/media/sms-concept.png
diff --git a/articles/communication-services/samples/media/create-new-agent.png b/articles/communication-services/samples/media/create-new-agent.png
diff --git a/articles/cost-management-billing/understand/mca-overview.md b/articles/cost-management-billing/understand/mca-overview.md
@@ -6,7 +6,7 @@ ms.reviewer: jkinma
 ms.service: cost-management-billing
 ms.subservice: billing
 ms.topic: conceptual
-ms.date: 04/27/2025
+ms.date: 11/10/2025
 ms.author: jkinma
 ---
 
diff --git a/articles/cost-management-billing/understand/mca-understand-your-invoice.md b/articles/cost-management-billing/understand/mca-understand-your-invoice.md
@@ -6,7 +6,7 @@ ms.reviewer: jkinma
 ms.service: cost-management-billing
 ms.subservice: billing
 ms.topic: conceptual
-ms.date: 05/14/2025
+ms.date: 11/10/2025
 ms.author: jkinma
 ---
 
diff --git a/articles/cost-management-billing/understand/review-partner-agreement-bill.md b/articles/cost-management-billing/understand/review-partner-agreement-bill.md
@@ -6,7 +6,7 @@ ms.reviewer: jkinma
 ms.service: cost-management-billing
 ms.subservice: billing
 ms.topic: tutorial
-ms.date: 04/22/2025
+ms.date: 11/10/2025
 ms.author: jkinma
 ---
 
diff --git a/articles/cost-management-billing/understand/understand-azure-marketplace-charges.md b/articles/cost-management-billing/understand/understand-azure-marketplace-charges.md
@@ -7,10 +7,10 @@ ms.reviewer: jkinma
 ms.service: cost-management-billing
 ms.subservice: billing
 ms.topic: conceptual
-ms.date: 05/01/2025
+ms.date: 11/10/2025
 ms.custom:
-  - build-2025
-  - sfi-image-nochange
+- build-2025
+- sfi-image-nochange
 ---
 
 # Understand your Azure external services charges
diff --git a/articles/dev-box/how-to-configure-dev-center-imaging.md b/articles/dev-box/how-to-configure-dev-center-imaging.md
diff --git a/articles/dev-box/media/how-to-configure-dev-center-imaging/dev-box-add-catalog-auto-build-image.png b/articles/dev-box/media/how-to-configure-dev-center-imaging/dev-box-add-catalog-auto-build-image.png
diff --git a/articles/security/develop/TOC.yml b/articles/security/develop/TOC.yml
@@ -60,6 +60,8 @@
         href: threat-modeling-tool-releases-73309251.md
       - name: Threat Modeling Tool update release 7.3.31026.3 - October 26 2023
         href: threat-modeling-tool-releases-73310263.md
+      - name: Threat Modeling Tool update release 7.3.51110.1 - November 10 2025
+        href: threat-modeling-tool-releases-73511101.md
     - name: Mitigations
       href: threat-modeling-tool-mitigations.md
       items:
diff --git a/articles/security/develop/threat-modeling-tool-releases-73511101.md b/articles/security/develop/threat-modeling-tool-releases-73511101.md
@@ -0,0 +1,55 @@
+---
+title: Microsoft Threat Modeling Tool release 7.3.51110.1 - Azure
+description: Documenting the release notes for the threat modeling tool release 7.3.51110.1.
+author: nishegde
+ms.author: nishegde
+ms.service: security
+ms.topic: article
+ms.date: 11/10/2025
+---
+
+# Threat Modeling Tool update release 7.3.51110.1 - 11/10/2025
+
+Version 7.3.51110 of the Microsoft Threat Modeling Tool (TMT) was released on November 10 2025 and contains the following changes:
+
+- Added a new safeguard that prevents users from saving `.tm7` and `.tb7` threat model files in the application's installation directory.
+    - When attempting to save files in the install directory, the tool now prompts users to select an alternative location, such as the user's Documents folder.
+    - The application remains open until the files are successfully moved out of Threat Modeling Tool's installation directory.
+  - This change was introduced to prevent accidental data loss after application updates when files are stored in the application directory. This ensures threat models are saved in user-accessible locations.
+- Bug fixes
+- Accessibility fixes
+
+## Known issues
+
+### Errors related to `TMT7.application` file deserialization
+
+#### Issue
+
+Some customers have reported receiving the following error message when downloading the Threat Modeling Tool:
+
+```
+The threat model file '$PATH\TMT7.application' could not be deserialized. File is not an actual threat model or the threat model may be corrupted.
+```
+
+This error occurs because some browsers don't natively support ClickOnce installation. In those cases, the ClickOnce application file is downloaded to the user's hard drive.
+
+#### Workaround
+
+This error will continue to appear if the Threat Modeling Tool is launched by double-clicking on the `TMT7.application` file. However, after bypassing the error the tool functions normally. Rather than launching the Threat Modeling Tool by double-clicking the `TMT7.application` file, users should utilize shortcuts created in the Windows Menu during the installation to start the Threat Modeling Tool.
+
+## System requirements
+
+- Supported Operating Systems
+  - [Microsoft Windows 10 Anniversary Update](https://blogs.windows.com/windowsexperience/2016/08/02/how-to-get-the-windows-10-anniversary-update/#HTkoK5Zdv0g2F2Zq.97) or later
+- .NET Version Required
+  - [.NET 4.7.1](https://go.microsoft.com/fwlink/?LinkId=863262) or later
+- Other Requirements
+  - An Internet connection is required to receive updates to the tool and templates.
+
+## Documentation and feedback
+
+- Documentation for the Threat Modeling Tool is located on [docs.microsoft.com](./threat-modeling-tool.md), and includes information [about using the tool](./threat-modeling-tool-getting-started.md).
+
+## Next steps
+
+Download the latest version of the [Microsoft Threat Modeling Tool](https://aka.ms/threatmodelingtool).
diff --git a/articles/security/develop/threat-modeling-tool-releases.md b/articles/security/develop/threat-modeling-tool-releases.md
@@ -27,6 +27,7 @@ The Microsoft Threat Modeling Tool is currently released as a free [click-to-dow
 
 ## Release Notes
 
+- [Microsoft Threat Modeling Tool GA Release Version 7.3.51110.1](threat-modeling-tool-releases-73511101.md) - November 10 2025
 - [Microsoft Threat Modeling Tool GA Release Version 7.3.31026.3](threat-modeling-tool-releases-73310263.md) - October 26 2023
 - [Microsoft Threat Modeling Tool GA Release Version 7.3.30925.1](threat-modeling-tool-releases-73309251.md) - September 25 2023
 - [Microsoft Threat Modeling Tool GA Release Version 7.3.30829.1](threat-modeling-tool-releases-73308291.md) - August 30 2023
diff --git a/articles/storage/elastic-san/elastic-san-connect-windows.md b/articles/storage/elastic-san/elastic-san-connect-windows.md
@@ -1,31 +1,67 @@
 ---
 title: Connect to an Azure Elastic SAN volume - Windows
-description: Learn how to connect to an Azure Elastic SAN volume from an individual Windows client using iSCSI and ensure optimal performance.
+description: Learn how to connect to an Azure Elastic SAN volume by using the Windows VM Extension or the manual connect script.
 author: roygara
 ms.service: azure-elastic-san-storage
 ms.topic: how-to
-ms.date: 06/18/2025
+ms.date: 11/10/2025
 ms.author: rogarana
 ms.custom: references_regions
-# Customer intent: "As a Windows client user, I want to connect to an Azure Elastic SAN volume using iSCSI, so that I can ensure optimal performance and manage multiple I/O sessions efficiently."
 ---
-
 # Connect to Elastic SAN volumes - Windows
 
-This article explains how to connect to an Elastic SAN volume from an individual Windows client. For details on connecting from a Linux client, see [Connect to Elastic SAN volumes - Linux](elastic-san-connect-linux.md).
+This article explains how to connect a Windows client to an Azure Elastic SAN volume. For details on connecting from a Linux client, see [Connect to Elastic SAN volumes - Linux](elastic-san-connect-linux.md).
+
+There are two connection options:
+
+- Elastic SAN VM extension– Use when deploying new VMs or Virtual Machine Scale Sets to automatically set up SAN connectivity for all instances. Ideal for large-scale, uniform environments, onboarding via the Azure portal, or when you want minimal manual steps.
+- Manual connect script – Use for existing VMs, advanced configurations, or when you need custom parameters (like specific session counts or unique volume mappings). Best for one-off setups or troubleshooting.
+
+Choose the option that best fits your deployment scenario. Both approaches require a deployed Elastic SAN resource and configured volume groups.
+
+## Connect during VM deployment using the Elastic SAN VM extension
+
+When you deploy a VM or a Virtual Machine Scale Set, you can use an Elastic SAN VM extension to greatly simplify the setup and configuration process for an Elastic SAN with that VM or the Virtual Machine Scale Set. When you apply the extension at the Virtual Machine Scale Set level, it ensures that all VMs in that scale set have uniform connectivity to your Elastic SAN. If you're going to create new infrastructure for an Elastic SAN, use the VM extension to configure the connections to your Elastic SAN.
+
+
+### Prerequisites
+
+- [Deploy an Elastic SAN](elastic-san-create.md)
+- Either [configure private endpoints](elastic-san-configure-private-endpoints.md) or [configure service endpoints](elastic-san-configure-service-endpoints.md)
+  
+### How to Use the VM Extension
+#### During VM Creation
+
+1. Sign in to the [Azure portal](https://portal.azure.com/).
+1. Create a new VM, fill in all the required values, and navigate to the **Extensions tab** during VM deployment.
+1. Select the **Elastic SAN VM extension** from the Marketplace.
+1. Fill in the required parameters for the Elastic SAN's name, the volume group name, the number of sessions, and the connection mode.
+- After the VM is deployed, navigate to that VM's **Extensions + applications** and update any settings as needed.
+
+#### Post-deployment configuration
+
 
-In this article, you configure your volume group to allow connections from your subnet and then you configure your client environment to connect to an Elastic SAN volume and establish an iSCSI connection. For best performance, ensure that your VM and your Elastic SAN are in the same zone.
 
-You must use a cluster manager when connecting an individual Elastic SAN volume to multiple clients. For details, see [Use clustered applications on Azure Elastic SAN](elastic-san-shared-volumes.md).
 
-## Prerequisites
+
+
+## Manually connect to Elastic SAN volumes
+
+This section explains how to connect to an Elastic storage area network (SAN) volume from an individual Windows client. For details on connecting from a Linux client, see [Connect to Elastic SAN volumes - Linux](elastic-san-connect-linux.md).
+
+In this section, you configure your client environment to connect to an Elastic SAN volume and establish a connection. For best performance, ensure that your VM and your Elastic SAN are in the same zone.
+
+When using the VM extension with Virtual Machine Scale Sets, each VM in the scale set is automatically connected to the Elastic SAN volume. If multiple VMs will access the same volume, you must use a cluster manager to coordinate shared access and maintain data consistency. For details, see [Use clustered applications on Azure Elastic SAN](elastic-san-shared-volumes.md).
+
+### Prerequisites
 
 - Use either the [latest Azure CLI](/cli/azure/install-azure-cli) or install the [latest Azure PowerShell module](/powershell/azure/install-azure-powershell)
 - [Deploy an Elastic SAN](elastic-san-create.md)
 - Either [configure private endpoints](elastic-san-configure-private-endpoints.md) or [configure service endpoints](elastic-san-configure-service-endpoints.md)
 
-## Enable iSCSI Initiator
 
+### Set up your client environment
+#### Enable iSCSI Initiator
 To create iSCSI connections from a Windows client, confirm the iSCSI service is running. If it's not, start the service, and set it to start automatically.
 
 ```powershell
@@ -39,7 +75,7 @@ Start-Service -Name MSiSCSI
 Set-Service -Name MSiSCSI -StartupType Automatic
 ```
 
-## Install Multipath I/O
+#### Install Multipath I/O
 
 To achieve higher IOPS and throughput to a volume and reach its maximum limits, you need to create multiple-sessions from the iSCSI initiator to the target volume based on your application's multi-threaded capabilities and performance requirements. You need Multipath I/O to aggregate these multiple paths into a single device, and to improve performance by optimally distributing I/O over all available paths based on a load balancing policy.
 
@@ -60,9 +96,9 @@ Enable-MSDSMAutomaticClaim -BusType iSCSI
 mpclaim -L -M 2
 ```
 
-## Attach volumes to the client
+#### Attach volumes to the client
 
-Use the following script to create your connections. To execute it, collect or determine the following parameters: 
+You can use the following script to create your connections. To execute it, you require the following parameters: 
 - $rgname: Resource Group Name
 - $esanname: Elastic SAN Name
 - $vgname: Volume Group Name
@@ -77,12 +113,11 @@ Copy the script from [here](https://github.com/Azure-Samples/azure-elastic-san/b
 ./connect.ps1 $rgname $esanname $vgname $vol1,$vol2,$vol3 32
 ```
 
-### Set session number
+Verify the number of sessions your volume has with either `iscsicli SessionList` or `mpclaim -s -d`
 
-Before you run the script, determine how many sessions your volume needs. To be able to reach a volume's highest IOPS and throughput capacities, you'll need 32 sessions. But, because Windows iSCSI initiator has a maximum of 256 sessions, you may need to use fewer than 32 sessions if you're connecting more than eight volumes to a Windows client.
+#### Number of sessions
 
-> [!NOTE]
-> Use the `-NumSession` parameter to set the number of sessions. The parameter accepts values from 1 to 32, and has a default value of 32.
+You need to use 32 sessions to each target volume to achieve its maximum IOPS and/or throughput limits. Windows iSCSI initiator has a limit of maximum 256 sessions. If you need to connect more than 8 volumes to a Windows client, reduce the number of sessions to each volume.
 
 
 ```bash
@@ -96,6 +131,13 @@ Before you run the script, determine how many sessions your volume needs. To be
 
   -VolumeName "<volume1>", "<volume2>" ` 
 
+  -NumSession “<value>”
+
+## Next steps
+
+[Configure Elastic SAN networking](elastic-san-networking.md)
+
+
   -NumSession “<value>”
 ```
 
diff --git a/articles/virtual-network/ip-services/manage-custom-ip-address-prefix.md b/articles/virtual-network/ip-services/manage-custom-ip-address-prefix.md
@@ -37,7 +37,7 @@ This article explains how to:
 For information on provisioning an IP address, see [Create a custom IP address prefix - Azure portal](create-custom-ip-address-prefix-portal.md), [Create a custom IP address prefix - Azure PowerShell](create-custom-ip-address-prefix-powershell.md), or [Create a custom IP address prefix - Azure CLI](create-custom-ip-address-prefix-cli.md).
 
 > [!NOTE]
-> The examples below primarily reference the "unified" model for custom IP prefixes. For decommissoning and deprovisioning of custom IP prefixes using the "global/regional" model, see the special section at the end of this page.
+> The examples below primarily reference the "unified" model for custom IP prefixes. For decommissioning and deprovisioning of custom IP prefixes using the "global/regional" model, see the [special section at the end of this page](#removal-of-prefixes-using-the-globalregional-model).
 
 ## Create a public IP prefix from a custom IP prefix
 
