Merge pull request #295504 from MicrosoftDocs/main

ttorble · web-flow · commit 881b95ddead8 · 2025-02-28T12:16:21.000Z
Publish to live, Friday 4 AM PST, 2/28
diff --git a/articles/active-directory-b2c/multi-factor-authentication.md b/articles/active-directory-b2c/multi-factor-authentication.md
@@ -133,6 +133,19 @@ In Azure AD B2C, you can delete a user's TOTP authenticator app enrollment. The
 
 Learn how to [delete a user's Software OATH token authentication method](/graph/api/softwareoathauthenticationmethod-delete) using the Microsoft Graph API.
 
+### SMS pricing tiers by country/region
+
+The following table provides details about the different pricing tiers for SMS based authentication services across various countries or regions. For pricing details, see [Azure AD B2C pricing](https://azure.microsoft.com/pricing/details/active-directory-b2c/).
+
+SMS is an add-on feature and requires a linked subscription. If your subscription expires or is cancelled, end users will no longer be able to authenticate using SMS, which could block them from signing in depending on your MFA policy.
+
+|Tier                               |Countries/Regions  |
+|-----------------------------------|-------------------|
+|Phone Authentication Low Cost      |Australia, Brazil, Brunei, Canada, Chile, China, Colombia, Cyprus, North Macedonia, Poland, Portugal, South Korea, Thailand, Türkiye, United States         |
+|Phone Authentication Mid Low Cost  |Greenland, Albania, American Samoa, Austria, Bahamas, Bahrain, Bosnia & Herzegovina, Botswana, Costa Rica, Czech Republic, Denmark, Estonia, Faroe Islands, Finland, France, Greece, Hong Kong SAR, Hungary, Iceland, Ireland, Italy, Japan, Latvia, Lithuania, Luxembourg, Macao SAR, Malta, Mexico, Micronesia, Moldova, Namibia, New Zealand, Nicaragua, Norway, Romania, São Tomé and Príncipe, Seychelles Republic, Singapore, Slovakia, Solomon Islands, Spain, Sweden, Switzerland, Taiwan, United Kingdom, United States Virgin Islands, Uruguay         |
+|Phone Authentication Mid High Cost |Andorra, Angola, Anguilla, Antarctica, Antigua and Barbuda, Argentina, Armenia, Aruba, Barbados, Belgium, Benin, Bolivia, Bonaire, Curaçao, Saba, Sint Eustatius and Sint Maarten, British Virgin Islands, Bulgaria, Burkina Faso, Cameroon, Cayman Islands, Central African Republic, Cook Islands, Côte d’Ivoire, Croatia, Diego Garcia, Djibouti, Dominican Republic, Dominican Republic, Dominican Republic, Ecuador, El Salvador, Eritrea, Falkland Islands, Fiji, French Guiana, French Polynesia, Gambia, Georgia, Germany, Gibraltar, Grenada, Guadeloupe, Guam, Guinea, Guyana, Honduras, India, Kenya, Kiribati, Laos, Liberia, Malaysia, Marshall Islands, Martinique, Mauritius, Monaco, Montenegro, Montserrat, Netherlands, New Caledonia, Niue, Oman, Palau, Panama, Paraguay, Peru, Puerto Rico, Puerto Rico, Réunion, Rwanda, Saint Helena, Ascension and Tristan de Cunha, Saint Kitts & Nevis, Saint Lucia, Saint Pierre & Miquelon, Saint Vincent and the Grenadines, Saipan, Samoa, San Marino, Saudi Arabia, Sint Maarten, Slovenia, South Africa, South Sudan, Suriname, Swaziland (New Name is Kingdom of Eswatini), Timor-Leste, Tokelau, Tonga, Turks & Caicos, Tuvalu, United Arab Emirates, Vanuatu, Venezuela, Vietnam, Wallis and Futuna         |
+|Phone Authentication High Cost     |Liechtenstein, Bermuda, Cabo Verde, Cambodia, Democratic Republic of Congo, Dominica, Egypt, Equatorial Guinea, Ghana, Guatemala, Guinea-Bissau, Israel, Jamaica, Jamaica, Kosovo, Lesotho, Maldives, Mali, Mauritania, Morocco, Mozambique, Papua New Guinea, Philippines, Qatar, Sierra Leone, Trinidad & Tobago, Ukraine, Zimbabwe, Afghanistan, Algeria, Azerbaijan, Bangladesh, Belarus, Belize, Bhutan, Burundi, Chad, Comoros, Congo, Ethiopia, Gabonese Republic, Haiti, Indonesia, Iraq, Jordan, Kuwait, Kyrgyzstan, Lebanon, Libya, Madagascar, Malawi, Mongolia, Myanmar, Nauru, Nepal, Niger, Nigeria, Pakistan, Palestinian National Authority, Russia, Senegal, Serbia, Somalia, Sri Lanka, Sudan, Tajikistan, Tanzania, Togolese Republic, Tunisia, Turkmenistan, Uganda, Uzbekistan, Yemen, Zambia         |
+
 ::: zone pivot="b2c-custom-policy"
 
 ## Next steps
diff --git a/articles/backup/backup-center-faq.yml b/articles/backup/backup-center-faq.yml
@@ -2,7 +2,7 @@
 metadata:
   title: Backup center - FAQ
   description: This article answers frequently asked questions about Backup center.
-  ms.date: 02/14/2022
+  ms.date: 02/28/2025
   ms.topic: faq
   ms.service: azure-backup
   author: jyothisuri
@@ -12,6 +12,9 @@ summary: This article answers frequently asked questions about Backup center.
 sections:
   - name: Management
     questions:
+      - question: How can I open Backup center from the Azure portal?
+        answer: |
+          You can now go to the Backup center from Azure Business Continuity Center. [Learn more](backup-center-overview.md#get-started-with-backup-center).
       - question: Can Backup center be used across tenants? 
         answer: |
           Yes, if you're using [Azure Lighthouse](/azure/lighthouse/overview) and have delegated access to subscriptions across different tenants, you can use Backup Center as a single pane of glass to manage backups across tenants.
diff --git a/articles/backup/blob-backup-support-matrix.md b/articles/backup/blob-backup-support-matrix.md
@@ -2,7 +2,7 @@
 title: Support matrix for Azure Blobs backup
 description: Provides a summary of support settings and limitations when backing up Azure Blobs.
 ms.topic: reference
-ms.date: 01/27/2025
+ms.date: 02/28/2025
 ms.custom: references_regions, engagement-fy24
 ms.service: azure-backup
 author: jyothisuri
@@ -62,7 +62,7 @@ Operational backup of blobs uses blob point-in-time restore, blob versioning, so
   - To back up any new containers that get created after backup configuration for the storage account, modify the protection of the storage account. These containers aren't backed up automatically.
 - The storage accounts to be backed up must contain *a minimum of one container*. If the storage account doesn't contain any containers or if no containers are selected, an error may appear when you configure backup.
 - If you stop protection (vaulted backup) on a storage account, it doesn't delete the object replication policy created on the storage account. In these scenarios, you need to manually delete the *OR policies*.
-- Cool and archived blobs are currently not supported.
+- Archive tier blob backup isn't supported. Cool and cold tier blobs are restored in hot tier. 
 - The backup operation isn't supported for blobs that are uploaded by using [Data Lake Storage APIs](/rest/api/storageservices/data-lake-storage-gen2).
 - When you delete and recreate a storage account with the same name, **Object Replication** doesn't recognize the change. As a result, future Recovery Points continue to include the older blobs and their versions.
 - Similarly, if you delete and recreate a container with the same name, **Object Replication** doesn't track the change, and future Recovery Points still include the previous blobs and versions.
diff --git a/articles/backup/install-mars-agent.md b/articles/backup/install-mars-agent.md
@@ -106,6 +106,13 @@ If you've already installed the agent on any machines, ensure you're running the
 To install and register  the MARRS agent, follow these steps:
 
 1. Run the *MARSagentinstaller.exe* file on the machines that you want to back up.
+
+   >[!Note]
+   >If you haven't selected the option **Give me updates for other Microsoft products when I update Windows** in **OS settings**, the following setting screen might appear. However, the automatic updates of MARS on Microsoft updates aren't currently implemented.
+   >
+   >  :::image type="content" source="./media/backup-configure-vault/setting-page.png" alt-text="Screenshot shows the settings page for MARS.":::
+
+
 1. In the MARS Agent Setup Wizard, select **Installation Settings**. There, choose where to install the agent, and choose a location for the cache. Then select **Next**.
    * Azure Backup uses the cache to store data snapshots before sending them to Azure.
    * The cache location should have free space equal to at least 5 percent of the size of the data you'll back up.
diff --git a/articles/backup/media/backup-configure-vault/setting-page.png b/articles/backup/media/backup-configure-vault/setting-page.png
diff --git a/articles/backup/whats-new.md b/articles/backup/whats-new.md
@@ -2,7 +2,7 @@
 title: What's new in the Azure Backup service
 description: Learn about the new features in the Azure Backup service.
 ms.topic: release-notes
-ms.date: 02/18/2025
+ms.date: 02/28/2025
 ms.service: azure-backup
 ms.custom:
   - ignite-2023
@@ -104,7 +104,7 @@ You can learn more about the new releases by bookmarking this page or by [subscr
 
 ## Azure Backup for Azure Database for PostgreSQL – Flexible Server is now generally available
 
-Azure Backup now provides improved backup and restore processes, reduced downtime, and increased efficiency for Azure Database for PostgreSQL - Flexible Server. This feature is now available in all Azure regions. You can manage the protection of the database by using the [Azure Business Continuity Center](../business-continuity-center/business-continuity-center-overview.md) in the Azure portal.
+Azure Backup now provides improved backup and restore processes, reduced downtime, and increased efficiency for Azure Database for PostgreSQL - Flexible Server. This feature is generally available in the following regions: East Asia, Central India, Southeast Asia, UK South, and UK West. However, this feature is currently in preview for other regions. You can manage the protection of the database by using the [Azure Business Continuity Center](../business-continuity-center/business-continuity-center-overview.md) in the Azure portal.
 
 The robust, scalable backup solution for Azure Database for PostgreSQL – Flexible Server allows you to meet  the needs of enterprises and developers alike, emphasizing comprehensive data protection and management.
 
diff --git a/articles/confidential-computing/multi-party-data.md b/articles/confidential-computing/multi-party-data.md
@@ -63,6 +63,11 @@ _Code integrity and confidential ledgers:_ With distributed ledger technology (D
 
 ## What are options to get started?
 
+### Azure Confidential Clean Rooms (Preview)
+[Azure Confidential Clean Rooms (ACCR)](./confidential-clean-rooms.md) is designed for organizations that need to share privacy sensitive data such as personally identifiable information (PII) or protected health information (PHI) securely with other organizations to derive business critical insights which can be securely fine-tuning your ML model with sensitive data from other organizations for improved accuracy or performing secure analytics on joint data with your partner organizations. ACCR uses confidential containers on Azure Container Instances to ensure that your data stays protected from other collaborators and from Azure operators. It has applications spanning multiple industries such as healthcare, advertising, banking and financial services and retail.
+
+You can enrol yourself for the ACCR preview by submititng this [form](https://aka.ms/ACCR-Preview-Onboarding).
+
 ### ACC platform offerings that help enable confidential cleanrooms
 Roll up your sleeves and build a data clean room solution directly on these confidential computing service offerings.
 
diff --git a/articles/databox/data-box-heavy-limits.md b/articles/databox/data-box-heavy-limits.md
@@ -22,7 +22,8 @@ Consider these limits as you deploy and operate your Azure Data Box Heavy device
 ## Data Box Heavy limits
 
 - Data Box Heavy can store a maximum of 1 billion files per node.
-- Data Box Heavy supports a maximum of 512 containers or shares per node in the cloud. The top-level directories within the user share become containers or Azure file shares in the cloud. 
+- Data Box Heavy supports a maximum of 512 containers or shares per node in the cloud. The top-level directories within the user share become containers or Azure file shares in the cloud.
+- Data Box currently does not support the scenario where the customer's data is actively changing during export
 
 ## Azure Storage limits
 
diff --git a/articles/databox/data-box-limits.md b/articles/databox/data-box-limits.md
@@ -47,6 +47,7 @@ Data Box caveats for an export order include:
 - Maximum filename size is 1,024 characters. Filenames that exceed this length aren't exported. 
 - Duplicate prefixes in the *xml* file (uploaded during order creation) are exported. Duplicate prefixes aren't ignored.
 - Page blobs and container names are case-sensitive. If the casing is mismatched, the blob and/or container won't be found.
+- Data Box currently does not support the scenario where the customer's data is actively changing during export
  
 
 ## Azure storage account size limits
diff --git a/articles/hdinsight/spark/apache-spark-perf.md b/articles/hdinsight/spark/apache-spark-perf.md
@@ -3,7 +3,7 @@ title: Optimize Spark jobs for performance - Azure HDInsight
 description: Show common strategies for the best performance of Apache Spark clusters in Azure HDInsight.
 ms.service: azure-hdinsight
 ms.topic: conceptual
-ms.date: 09/06/2024
+ms.date: 02/28/2025
 ---
 # Optimize Apache Spark applications in HDInsight
 
diff --git a/articles/hdinsight/spark/spark-best-practices.md b/articles/hdinsight/spark/spark-best-practices.md
@@ -3,7 +3,7 @@ title: Apache Spark guidelines on Azure HDInsight
 description: Learn guidelines for using Apache Spark in Azure HDInsight.
 ms.service: azure-hdinsight
 ms.topic: conceptual
-ms.date: 07/12/2024
+ms.date: 02/28/2025
 ---
 
 # Apache Spark guidelines
diff --git a/articles/operator-nexus/concepts-network-fabric-controller.md b/articles/operator-nexus/concepts-network-fabric-controller.md
@@ -173,7 +173,7 @@ For optimal performance and redundancy, it is recommended to utilize two Express
 
 **What types of NFC SKUs are available?**
 
-NFC supports various SKUs including Basic, Standard, and High Performance options.
+NFC supports the Standard SKU and uses virtual machines from the DSv3 family.
 
 **Is it possible to update the NFC with a new Express Route Circuit?**
 
diff --git a/articles/operator-nexus/concepts-network-fabric-read-only-commands.md b/articles/operator-nexus/concepts-network-fabric-read-only-commands.md
@@ -16,7 +16,7 @@ Troubleshooting network devices is a critical aspect of effective network manage
 
 ## Understanding read-only commands 
 
-RO commands serve as essential tools for network administrators. Unlike read-write (RW) commands that modify device configurations, RO commands allow administrators to gather diagnostic information without altering the device's state. These commands provide valuable insights into the device's status, configuration, and operational data. The RO command also supports using a customer-provided storage account for storing output files.
+RO commands serve as essential tools for network administrators. Unlike read-write (RW) commands that modify device configurations, RO commands allow administrators to gather diagnostic information without altering the device's state. These commands provide valuable insights into the device's status, configuration, and operational data. The RO command also supports using a customer-provided storage account for storing output files using api version 2024-06-15-preview.
 
 ## Read-only diagnostic API 
 
@@ -36,7 +36,8 @@ By using the read-only diagnostic API, network administrators can efficiently tr
 
 To use Network Fabric read-only commands, complete the following steps:
 
-- Provision the Nexus Network Fabric successfully. 
+- Provision the Nexus Network Fabric successfully.
+
 - Generate the storage URL.
 
     Refer to [Create a container](../storage/blobs/blob-containers-portal.md#create-a-container) to create a container.  
@@ -49,13 +50,16 @@ To use Network Fabric read-only commands, complete the following steps:
     > [!NOTE]
     > SAS URLs are short lived. By default, it is set to expire in eight hours. If the SAS URL expires, then the fabric must be re-patched. 
 
-
 - Provide the storage URL with WRITE access via a support ticket. 
 
     > [!NOTE]
     > The Storage URL must be located in a different region from the Network Fabric. For instance, if the Fabric is hosted in East US, the storage URL should be outside of East US. 
 
-Alternatively, you can bring your own storage for storing output files by following the steps outlined in the [Bring Your Own Storage for Network Fabric](howto-configure-bring-your-own-storage-network-fabric.md) guide
+- Bring your own storage account 
+    Users can bring your own storage for storing output files of runRO command by following the steps outlined in the [Bring Your Own Storage for Network Fabric](howto-configure-bring-your-own-storage-network-fabric.md) guide.
+
+>[!Note]
+> Starting with the 2024-06-15-preview API update, bringing your own storage account is the preferred method. Users should create or associate the fabric instances with your storage account referring to [configure Bring-Your-Own (BYO) Storage for Network Fabric](/articles/operator-nexus/howto-configure-bring-your-own-storage-network-fabric.md) article.
 
  ## Command restrictions
 
@@ -109,9 +113,7 @@ To troubleshoot using read-only commands, follow these steps:
     
     ```azurecli
     https://management.azure.com/subscriptions/xxxxxxxxxxx/providers/Microsoft.ManagedNetworkFabric/locations/EASTUS/operationStatuses/xxxxxxxxxxx?api-version=20XX-0X-xx-xx
-    ```
-
-    
+    ```    
 
 4. View and download the generated output file. Sample output is shown here.
 
diff --git a/articles/operator-nexus/concepts-network-fabric-read-write-commands.md b/articles/operator-nexus/concepts-network-fabric-read-write-commands.md
@@ -554,7 +554,7 @@ Expected output
 ```
 
 > [!Note]
-> RW configurations do not persist across upgrades. After an upgrade of Network Fabric, the rwDeviceConfig property will be empty unless the user manually reapplies the RW configuration.
+> RW configuration persists during a reboot without ZTP but does not persist upgrades, device RMA, or a reboot with ZTP. After these events, the rwDeviceConfig property is empty unless the user reapplies the RW configuration manually.
 
 ## Limitations 
 
diff --git a/articles/operator-nexus/how-to-validate-cables.md b/articles/operator-nexus/how-to-validate-cables.md
@@ -11,7 +11,7 @@ ms.date: 04/15/2024
 ---
 # Validate Cables for Nexus Network Fabric
 
-This article explains the  Fabric cable validation, where the primary function of the diagnostic API is to check all fabric devices for potential cabling issues. The Diagnostic API assesses whether the interconnected devices adhere to the Bill of Materials (BOM) and according to the resource Stock Keeping Units (SKUs), classifying them as compliant or noncompliant. Device types include Customer Edge (CE), Top of Rack (TOR), Management (MGMT), and Network Packet Broker (NPB) devices. The results are presented in a JSON format, encompassing details such as validation status, errors, identifier type, and neighbor device ID. These results are stored in a customer-provided Storage account. It's vital to the overall deployment that errors identified in this report are resolved before moving onto the Cluster deployment step.
+This article explains the  Fabric cable validation, where the primary function of the diagnostic API is to check all fabric devices for potential cabling issues. The Diagnostic API assesses whether the interconnected devices adhere to the Bill of Materials (BOM) and according to the resource Stock Keeping Units (SKUs), classifying them as compliant or noncompliant. Device types include Customer Edge (CE), Top of Rack (TOR), Management (MGMT), and Network Packet Broker (NPB) devices. The results are presented in a JSON format, encompassing details such as validation status, errors, identifier type, and neighbor device ID. These results are stored in a customer-provided Storage account. It's vital to the overall deployment that errors identified in this report are resolved before moving onto the Cluster deployment step. The calble validation also supports using a customer-provided storage account for storing output files using api version 2024-06-15-preview.
 
 For BOM details, refer to [Azure Operator Nexus SKUs](./reference-operator-nexus-skus.md)
 
@@ -24,6 +24,9 @@ For BOM details, refer to [Azure Operator Nexus SKUs](./reference-operator-nexus
   - `Storage Blob Data Contributor` role must be assigned to the `Nexus Network Fabric RP` with access assigned to the storage account.
 - Microsoft Support must patch the Nexus Network Fabric with an active storage SAS URL before running cabling validation.
 
+>[!Note]
+> Starting with the 2024-06-15-preview API update, bringing your own storage account is the preferred method. Users should create or associate the fabric instances with your storage account referring to [configure Bring-Your-Own (BYO) Storage for Network Fabric](/articles/operator-nexus/howto-configure-bring-your-own-storage-network-fabric.md) article.
+
 ## Creating an Azure Support Request for Patching Nexus Network Fabric:
   - Refer to [How to create an Azure support request](/azure/azure-portal/supportability/how-to-create-azure-support-request)
   - Enter `Nexus Network Fabric` for the issue and click `Go`.
diff --git a/articles/operator-nexus/howto-append-custom-suffix-to-interface-descriptions.md b/articles/operator-nexus/howto-append-custom-suffix-to-interface-descriptions.md
diff --git a/articles/operator-nexus/howto-configure-bring-your-own-storage-network-fabric.md b/articles/operator-nexus/howto-configure-bring-your-own-storage-network-fabric.md
diff --git a/articles/operator-nexus/howto-platform-prerequisites.md b/articles/operator-nexus/howto-platform-prerequisites.md
diff --git a/articles/operator-nexus/howto-reboot-network-device.md b/articles/operator-nexus/howto-reboot-network-device.md
diff --git a/articles/operator-nexus/howto-restrict-serial-port-access-and-set-timeout-on-terminal-server.md b/articles/operator-nexus/howto-restrict-serial-port-access-and-set-timeout-on-terminal-server.md
diff --git a/articles/virtual-desktop/users/client-features-web.md b/articles/virtual-desktop/users/client-features-web.md
