Merge pull request #313195 from MicrosoftDocs/main

Auto Publish – main to live - 2026-03-16 17:00 UTC

Author: learn-build-service-prod[bot]

articles/application-gateway/ssl-overview.md

@@ -5,7 +5,7 @@ services: application-gateway
 author: mbender-ms
 ms.service: azure-application-gateway
 ms.topic: concept-article
-ms.date: 02/16/2026
+ms.date: 03/13/2026
 ms.author: mbender
 
 # Customer intent: "As a cloud architect, I want to configure end to end TLS on the application gateway, so that I can ensure secure communication and compliance for sensitive data transmitted between clients and backend servers."
@@ -63,7 +63,7 @@ End-to-end TLS allows you to encrypt and securely transmit sensitive data to the
 
 When configured with end-to-end TLS communication mode, Application Gateway terminates the TLS sessions at the gateway and decrypts user traffic. It then applies the configured rules to select an appropriate backend pool instance to route traffic to. Application Gateway then initiates a new TLS connection to the backend server and re-encrypts data using the backend server's public key certificate before transmitting the request to the backend. Any response from the web server goes through the same process back to the end user. End-to-end TLS is enabled by setting protocol setting in [Backend HTTP Setting](./configuration-overview.md#backend-settings) to HTTPS, which is then applied to a backend pool.
 
-In Application Gateway v1 SKU gateways, [TLS policy](./application-gateway-ssl-policy-overview.md) applies the TLS version only to frontend traffic and the defined ciphers to both frontend and backend targets.  In Application Gateway v2 SKU gateways, TLS policy only applies to frontend traffic, backend TLS connections will always be negotiated via TLS 1.0 to TLS 1.2 versions.
+In Application Gateway v1 SKU gateways, [TLS policy](./application-gateway-ssl-policy-overview.md) applies the TLS version only to frontend traffic and the defined ciphers to both frontend and backend targets.  In Application Gateway v2 SKU, the TLS policy applies only to frontend traffic. Backend TLS connections are always negotiated using TLS 1.3, and if unavailable, fall back to TLS 1.2.
 
 Application Gateway only communicates with those backend servers that have either allow-listed their certificate with the Application Gateway or whose certificates are signed by well-known CA authorities and the certificate's CN matches the host name in the HTTP backend settings. These include the trusted Azure services such as Azure App Service/Web Apps and Azure API Management.
 

articles/cost-management-billing/manage/change-credit-card.md

@@ -6,7 +6,7 @@ ms.reviewer: souchak
 ms.service: cost-management-billing
 ms.subservice: billing
 ms.topic: how-to
-ms.date: 03/08/2026
+ms.date: 03/12/2026
 ms.author: souchak
 ms.custom:
 - references_regions
@@ -36,6 +36,11 @@ The Reserve Bank of India has a [regulation for storing credit card information]
 
 If you get an error after you add a credit card, see [Troubleshoot a declined card](../troubleshoot-billing/troubleshoot-declined-card.md).
 
+> [!NOTE]
+> Additional information for SEPA Direct Debit users in Europe:
+> - SEPA Direct Debit is connected to the specific billing account where it is set up. If you have multiple billing accounts and want to use SEPA Direct Debit, you need to add this payment method separately to each account.
+> - If you have an MCA billing account type, you must have Billing account owner or Billing account contributor role to add or manage SEPA Direct Debit payment method. You can learn more about administrative roles [here](understand-mca-roles.md).
+
 <a id="addcard"></a>
 
 ## Manage pay-as-you-go credit cards

articles/cost-management-billing/manage/supported-payment-methods.md

@@ -6,7 +6,7 @@ ms.reviewer: souchak
 ms.service: cost-management-billing
 ms.subservice: billing
 ms.topic: reference
-ms.date: 09/17/2025
+ms.date: 03/12/2026
 ms.author: souchak
 ms.custom:
 - references_regions

articles/migrate/end-to-end-portal-experience-server-migrations.md

@@ -0,0 +1,77 @@
+---
+title: Simplified End-to-End Migrations Experience in Azure Migrate
+description: Learn how the Azure Copilot migration agent (preview) helps you plan and analyze migrations using Azure Migrate data, providing insights on readiness, migration strategy, ROI, and landing zone options.
+ms.topic: how-to
+author: dhananjayanr98 
+ms.author: dhananjayanr
+ms.service: azure-migrate
+ms.reviewer: v-uhabiba
+ms.date: 03/13/2026
+monikerRange: migrate 
+Customer intent: This article is intended to guide users on leveraging the Azure Copilot migration agent for planning and analyzing migrations. It covers how the agent utilizes Azure Migrate data, outlines supported migration scenarios, details available capabilities, and provides example interactions to help users understand and execute migration processes effectively.
+---
+
+# Simplify end-to-end portal experience for server migrations with Azure Migrate
+
+Azure Migrate provides an enhanced portal experience for migrations that streamlines the end‑to‑end, application‑aware migration journey. This experience lets you move seamlessly through each stage of migration—from discovering your source environment to completing migrations to Azure, using a single, unified workflow.
+
+In this article, you'll learn  how to navigate the end-to-end portal to do the below activities for migrations:
+
+- Complete the required configuration for your source environment, and then start migration execution for servers discovered by using the Azure Migrate appliance.
+- You can track execution progress across the **Preparation**, **Testing**, and **Completion** stages.
+
+## Prerequisites  
+
+Before you begin, ensure the following:
+
+- You have installed the Azure Migrate appliance that matches your source environment **(VMware, Hyper‑V, or Physical)**. The Azure Migrate appliance is required to use the end‑to‑end portal experience, from discovery through migration.
+
+- You have completed server discovery by using the installed Azure Migrate appliance.
+
+- For more information, see the following tutorials:
+    - [Tutorial: Discover servers running in a VMware environment with Azure Migrate](tutorial-discover-vmware.md).
+    - [Tutorial: Discover servers running on Hyper-V with Azure Migrate: Discovery and assessment](tutorial-discover-hyper-v.md).
+    - [Discover physical servers and servers running in AWS and GCP](tutorial-discover-physical.md)
+
+    >[!NOTE]
+    > Use the link on the Migrations page by navigating to **Execute** > **Migrations** in your Azure Migrate Project to switch to the classic portal for discovery and execution of agent-based and Hyper-V migrations using the replication appliance without the Azure Migrate appliance. These servers will not be visible for tracking in the end-to-end portal experience. We recommend starting discovery with the Azure Migrate appliance to take advantage of the benefits of the end-to-end portal experience. 
+
+## Execute migrations using the end-to-end portal
+
+This section explains how to start execution for your servers discovered using the Azure Migrate appliance. Follow the steps below to start migration execution from your Azure Migrate project. 
+
+To start migration execution from your Azure Migrate project, follow the steps:
+
+1. In Azure Migrate project, go to **Execute** > **Migrations**, and then select **Start execution**.
+1. On the **Specify intent** pane, select **Servers** or **Virtual machines (VMs)**, and choose Azure VM as the target. You can either select an existing assessment or manually select servers from the discovered inventory.
+1. Under **Discovery method**, select the appliance that matches your source environment **(VMware, Hyper‑V, or Physical)**. Only appliances that are already configured appear in the list.
+
+    - **VMware agentless**: Select the **VMware appliance**, select **Agentless migration**, and then select **Continue**.
+    - **Hyper-V**: Select the Hyper-V appliance. If the replication provider isn’t already installed, install it on the Hyper-V hosts to enable replication. After you configure the provider by using the provided link, continue to the next step.
+    - **Physical servers and VMware agent-based**: Set up the replication appliance (covered in the next step), and then select **Continue**.
+1. In **Workloads**, select the servers that you want to replicate, and configure the required settings.
+
+    - For **VMware agent-based and physical servers**, select the **replication appliance** if it’s already configured. If this is the first time you’re running agent-based migrations in the project, select **Set up the replication appliance** and complete the registration by following the steps from [tutorial migrate physical vitural machines](tutorial-migrate-physical-virtual-machines.md#simplified-experience-recommended).
+    
+1. Complete the remaining configuration for **Target, Compute, Disk**, and **Tags**, review your settings, and then select **Execute migration**. The selected servers move into execution and are available for tracking.
+
+## Track migrations using end-to-end portal
+
+This section explains how to track server migrations in the new Azure Migrate experience, including viewing execution stages, tracking status, and taking required actions during each phase.
+
+To track migration progress for your servers, follow the steps:
+
+1. To track migrations, go to **Execute** > **Migrations**. Use **View by applications** or **View by workloads** to switch how items are grouped.
+2. Execution progress is shown in **Execution stage** and **Execution status**:
+    - **Execution stage**: Preparation, Testing, or Completion.
+    - **Execution status**: In progress, In error, Action pending, or Completed.
+3. Select a server to open the detailed view. Use the drop-down menus to review status and take actions.
+4. The Execution progress is tracked across three stages in the Execution stage:
+    - **Preparation**: Servers that are enabled for replication remain in the Preparation stage while initial replication (data replication) is in progress. After initial replication is complete, the servers move to the Testing stage.
+    - **Testing**: Servers for which initial replication is complete and delta replication is in progress appear in this stage. Use this stage to run test migrations (recommended). Ensure that you clean up test migrations after validation. You can skip the Testing stage and start migration directly by using the actions available in the **Completion** drop-downs.
+    - **Completion**: Servers for which testing is completed or skipped appear at this stage. From the Completion drop-down menu (available when you select a server), you can start migration and complete migration.
+    After migration finishes, ensure that you select **Complete Migration** to clean up resources and shut down the source virtual machines.
+
+## Related content
+
+[Learn more](server-migrate-overview.md) about different migration methods in Azure Migrate. 

articles/migrate/toc.yml

@@ -376,6 +376,8 @@ items:
       href: /azure/lighthouse/how-to/migration-at-scale?toc=/azure/migrate/toc.json&bc=/azure/migrate/breadcrumb/toc.json
   - name: VMware migrations with migration agent
     href: how-to-plan-analyze-migration-with-agent.md
+  - name: End-to-end portal experience for server migrations with Azure Migrate
+    href: end-to-end-portal-experience-server-migrations.md
 - name: Troubleshoot
   items:
   - name: Azure Migrate Project

articles/migrate/whats-new.md

@@ -16,6 +16,7 @@ ms.custom: mvc, engagement-fy25
 
 [Azure Migrate](migrate-services-overview.md) helps you discover, assess, and migrate on-premises servers, apps, and data to the Azure cloud platform. This article summarizes new releases and features in Azure Migrate.
 
+
 ## Update (March 2026)
 
 - Public preview: Azure Migrate now offers Azure Copilot migration agent, which provides a conversational experience to help you plan and analyze VMware migrations using Azure Migrate data. You can use natural language prompts to explore inventory, assess readiness, and evaluate migration strategies and business cases, while migration execution continues in the Azure Migrate portal. [Learn more](azure-copilot-migration-agent.md).