Merge pull request #307527 from MicrosoftDocs/main

10/29/2025 AM Publish

Author: Taojunshen

articles/azure-resource-manager/management/move-limitations/app-service-move-limitations.md

@@ -3,7 +3,7 @@ title: Move Azure App Service resources across resource groups or subscriptions
 description: Use Azure Resource Manager to move App Service resources to a new resource group or subscription.
 ms.topic: conceptual
 ms.custom: devx-track-arm-template
-ms.date: 09/15/2025
+ms.date: 10/29/2025
 ---
 
 # Move App Service resources to a new resource group or subscription
@@ -71,7 +71,7 @@ When you create a new App Service plan with zone redundancy enabled, it's deploy
 
 If your App Service plan is on a scale unit that doesn't support zone redundancy, you can't enable zone redundancy on your plan. Instead, you need to:
 
-1. Create a new App Service plan in a new resource group. When you create a new App Service plan with zone redundancy enabled in a different resource group, it's deployed to a different scale unit.
+1. Create a new App Service plan **with zone redundancy explicitly selected at the time the new App Service plan is created** in a new resource group. When you create a new App Service plan with zone redundancy enabled in a different resource group, it's deployed to a different scale unit.
 1. Redeploy your apps to the new plan. When you create a new plan that's on a different scale unit, you need to redeploy your apps. You can't move apps between plans that are on different scale units.
 
 For more information about zone redundancy requirements and scale units, see [Reliability in Azure App Service](/azure/reliability/reliability-app-service#availability-zone-support).

articles/azure-vmware/azure-vmware-solution-known-issues.md

@@ -4,7 +4,7 @@ description: This article provides details about the known issues of Azure VMwar
 ms.topic: reference
 ms.custom: "engagement-fy23"
 ms.service: azure-vmware
-ms.date: 10/8/2025
+ms.date: 10/22/2025
 # Customer intent: "As a cloud administrator, I want to access detailed information about known issues in Azure VMware Solution so that I can implement workarounds and ensure the stability of my virtual environment."
 ---
 
@@ -16,6 +16,7 @@ Refer to the table to find details about resolution dates or possible workaround
 
 |Issue | Date discovered | Workaround | Date resolved |
 | :------------------------------------- | :------------ | :------------- | :------------- |
+| Azure VMware Solution hosts and associated VMs may become unresponsive due to an [ESXi Mellanox driver issue](https://knowledge.broadcom.com/external/article/383273). | October 22, 2025 | Microsoft is actively monitoring and mitigating this issue and notifying all impacted customers that an urgent upgrade is necessary to remediate this issue. | October 22, 2025 - Resolved in [ESXi 8.0_U3f](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/release-notes/esxi-update-and-patch-release-notes/vsphere-esxi-80u3f-release-notes.html) |
 | Compression and deduplication are disabled by default in vSAN OSA-based clusters. This behavior is observed starting from Cluster-2 onwards, whereas Cluster-1 was deployed with the default configuration. | September 29, 2025 | To remediate, use existing Set-vSANCompressDedupe Run command to enable Compression and Deduplication. Click the [link](https://learn.microsoft.com/azure/azure-vmware/configure-vsan#set-vmware-vsan-space-efficiency) to learn more about Set-vSANCompressDedupe cmdlet. | N/A |
 | [VMSA-2025-0016](https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/36150) VMware vCenter Server and NSX updates address multiple vulnerabilities (CVE-2025-41250, CVE-2025-41251, CVE-2025-41252). | September 29, 2025 | These vulnerabilities do not apply to Azure VMware Solution since we have existing compensating controls to mitigate the risk of exploitation. | N/A |
 | [VMSA-2025-0015](https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/36149) VMware Aria Operations and VMware Tools updates address multiple vulnerabilities (CVE-2025-41244, CVE-2025-41245, CVE-2025-41246). | September 29, 2025 | Microsoft has confirmed these vulnerabilities affect Azure VMware Solution. Microsoft strongly recommends immediately upgrading VMware Aria Operations and VMware Tools for remediation. To remediate CVE-2025-41244, apply version 12.5.4 or 13.0.5 of VMware Tools using the Azure VMware Solution Run command ``Set-Tools-Repo.`` | September 29, 2025 |

articles/cost-management-billing/toc.yml

@@ -25,6 +25,8 @@
     href: understand/understand-usage.md
   - name: Individual subscription invoice terms
     href: understand/understand-invoice.md
+  - name: Understand the billing and tenant relationship
+    href: understand/understand-billing-tenant-relationship.md  
   - name: Microsoft Customer Agreement usage terms
     href: understand/mca-understand-your-usage.md
   - name: Microsoft Customer Agreement invoice terms

articles/cost-management-billing/understand/media/understand-billing-tenant-relationship/azure-billing-tenant-relationship.png

@@ -0,0 +1,71 @@
+---
+title: Understand the billing tenant relationship
+description: Learn about the billing tenant relationship in Azure and how it affects your billing and subscription management.
+keywords: billing tenant,azure billing,subscription management,billing relationship
+author: chrisdoofer
+ms.reviewer: jkinma
+ms.service: cost-management-billing
+ms.subservice: billing
+ms.topic: conceptual
+ms.date: 09/07/2025
+ms.author: chbenne
+---
+
+# Billing and tenant relationship
+
+:::image type="content" source="./media/understand-billing-tenant-relationship/azure-billing-tenant-relationship.png" alt-text="Diagram that shows the relationship between a billing contract and associated tenant and subsequent subscriptions." border="false":::
+
+## Customer to contract
+
+Customer Organizations can sign multiple contracts with Microsoft. Even though it is advised to have a 1:1 relationship between Customer and Microsoft contract, Customer's can theoretically use multiple contracts at the same time.
+
+### Example
+
+The best example for this scenario is during a transition period from an Enterprise Agreement (EA) to Microsoft Customer Agreement (MCA), where the customer has an active EA and an active MCA contract. During merger and acquisition (M&A) activities, a customer organization might end up with multiple EA or MCA contracts.
+
+## Contract to price sheet
+
+Every contract is associated with a customer specific price sheet. This determines the individual customer prices in the agreed billing currency. In an MCA, the default associated price sheet equals the Azure Retail price list in USD. The price sheet can be accessed in the Azure portal.
+
+## Contract to Microsoft Azure Consumption Commitment (MACC)
+
+Customers can sign a MACC. There is usually a 1:1 relationship between a contract and a MACC. As a benefit of this commitment, Customers might get discounted pricing on Azure Resources (usage). The discount is reflected in the price sheet associated with the contract.
+
+## Contract to billing roles
+
+Both EA and MCA provide Customers with roles, that can manage certain aspects of the contract. These roles are called billing roles. Billing roles differ from EA to MCA and are described in detail here for EA and here for MCA. A key difference between EA and MCA is, that Customers can associate any valid work, school, or Microsoft account to EA billing roles but only work accounts of an approved tenant for MCA.
+
+## Contract to tenant
+
+To manage billing roles, customers must associate exactly one Entra ID tenant with the contract, this action must be completed at the time the contract is setup. Identities within this Tenant can be assigned to billing roles within the contract.
+
+### Example
+
+User Dirk from the contoso.com tenant can be assigned to the EA admin role in Contoso’s EA contract.
+
+In MCA, this tenant is called the primary billing tenant. Only users from this tenant can be assigned to billing roles within the MCA contract.
+
+⚠️ **Warning**
+The tenant global administrator role is above the billing account administrator. Global administrators in a Microsoft Entra ID tenant can add or remove themselves as billing account administrators at any time to the Microsoft Customer Agreement.
+
+If you want to assign identities from tenants other than the primary billing tenant, you can add associated billing tenants.
+
+ℹ️ **Information**
+Even though customers should strive for a single tenant, there is no restriction in how many tenants a customer can create within a contract.
+
+## Contract to subscription
+
+An Azure subscription is a logical container used to provision and manage Azure resources. Resource access is managed through a trust relationship to an Entra ID tenant and billing is managed via a billing relationship to a Microsoft contract (EA or MCA). Every subscription can only have one billing relationship to one contract. This billing relationship can be moved to a different contract based on certain conditions (for example, in EA/MCA transition scenarios or M&A scenarios).
+
+Every contract can manage 5000 subscriptions by default.
+
+ℹ️ **Information**
+The billing relationship determines the prices for the consumed resources within the subscription. If you have a subscription that is associated with a contract that uses Azure retail prices you pay the retail price. If the associated contract has customer specific prices (for example, by signing a MACC with applicable discounts), the resources within this subscription are charged at these prices.
+
+## Subscription to tenant
+
+Every subscription has a 1:1 trust relationship to an Entra ID tenant. This trust relationship determines, which identities can manage the resources within the subscription.
+
+## Tenant to subscription
+
+Every tenant can manage trust relationships with virtually unlimited number of subscriptions. These subscriptions can use billing relationships to multiple contracts, which might lead to different prices for resources deployed to these subscriptions.

articles/cost-management-billing/understand/understand-billing-tenant-relationship.md

@@ -1,6 +1,6 @@
 ---
 title: Microsoft Dev Box capabilities are coming to Windows 365
-description: Discover how Microsoft Dev Box capabilities are transitioning to Windows 365, offering unified solutions for developers and IT admins starting November 2025.
+description: Discover how Microsoft Dev Box capabilities are transitioning to Windows 365, offering unified solutions for developers and IT admins starting in November 2025.
 #customer intent: As an IT admin, I want to understand the changes to Microsoft Dev Box so that I can plan for the transition to Windows 365.
 author: RoseHJM
 ms.author: rosemalcolm
@@ -10,8 +10,6 @@ ms.topic: concept-article
 ms.service: dev-box
 ---
 
-
-
 # Microsoft Dev Box capabilities are coming to Windows 365
 
 Microsoft Dev Box is evolving and transitioning into a unified business model under Windows 365. This transition reflects feedback from customers who asked for: 
@@ -21,20 +19,20 @@ Microsoft Dev Box is evolving and transitioning into a unified business model un
 - Access to a broader range of options, including GPU-backed SKUs. 
 - Greater flexibility to support hybrid and ephemeral development scenarios. 
 
-Windows 365 delivers personalized, persistent Cloud PCs to meet the needs of organizations of all sizes, supporting a broad range of employee personas and business scenarios. The Microsoft Dev Box service in Azure extends this vision by providing ready-to-code, cloud-powered development environments that enable developers to quickly spin up secure, ready-to-code, project-specific workspaces optimized for productivity. 
+Windows 365 delivers personalized, persistent Cloud PCs to meet the needs of organizations of all sizes, supporting a broad range of employee personas and business scenarios. The Microsoft Dev Box service in Azure extends this vision by providing cloud-powered, ready-to-code development environments that enable developers to quickly spin up secure, project-specific workspaces optimized for productivity. 
 
 We're excited to announce that we're bringing these developer-specific capabilities to Windows 365, further empowering organizations to deliver the best information worker and developer experiences from a single unified solution. 
 
-Dev Box is built on Windows 365, and by consolidating these capabilities into Windows 365 and unifying the solution, developers will benefit from a consistent, flexible solution, and seamless integration with enterprise identity and security. IT admins and platform engineers can use more centralized controls, streamlined provisioning, consistent policy enforcement, and unified visibility across Cloud PCs—from task workers to developers—all in one place. 
+Dev Box is built on Windows 365, and by consolidating these capabilities into Windows 365 and unifying the solution, developers will benefit from a consistent, flexible solution and seamless integration with enterprise identity and security. IT admins and platform engineers can use centralized controls, streamlined provisioning, consistent policy enforcement, and unified visibility across Cloud PCs—from task workers to developers—all in one place. 
 
 Effective November 1, 2025, the following changes will take place: 
 
 - The Microsoft Dev Box service stops accepting net new customers. 
     - *Net new customers* are defined as those with no prior Dev Box deployment in any form. 
     - As features are integrated into Windows 365 and made available publicly, Customers interested in continuing to leverage these capabilities should reach out to their Microsoft account team. 
 - There's no immediate change to existing customers 
-    - Customers who have run a POC, experimented, or begun configuring Dev Box are considered as existing customers and they can continue using and scaling their current Dev Box deployments. 
-    - If you plan to start using or scaling Dev Boxes into additional tenants, submit a request through [Azure Support](https://go.microsoft.com/fwlink/p/?linkid=2202692&clcid=0x409) to your new tenants allowlisted.  
+    - Customers who have run a POC, experimented, or begun configuring Dev Box are considered existing customers, and they can continue using and scaling their current Dev Box deployments. 
+    - If you plan to start using or scaling Dev Boxes into additional tenants, submit a request through [Azure Support](https://go.microsoft.com/fwlink/p/?linkid=2202692&clcid=0x409) to get your new tenants allowlisted.  
 
 All core workflows and value props remain intact - including managing development teams through the Dev Center/Project platform in Azure, configuring guardrails, providing self-serve capabilities for developers, and offering ready-to-code machines with imaging and customizations, as well as custom network support.