Merge pull request #264316 from MicrosoftDocs/main

Publish to live, Friday 4 AM PST, 1/26

Author: ttorble

articles/azure-maps/release-notes-map-control.md

@@ -16,6 +16,16 @@ This document contains information about new features and other changes to the M
 
 ## v3 (latest)
 
+### [3.1.1] (January 26, 2024)
+
+#### New features (3.1.1)
+
+- Added a new option, `enableAccessibilityLocationFallback`, to enable or disable reverse-geocoding API fallback for accessibility (screen reader).
+
+#### Bug fixes (3.1.1)
+
+- Resolved an issue where ApplicationInsights v3.0.5 was potentially sending a large number of requests.
+
 ### [3.1.0] (January 12, 2024)
 
 #### New features (3.1.0)
@@ -548,6 +558,7 @@ Stay up to date on Azure Maps:
 > [!div class="nextstepaction"]
 > [Azure Maps Blog]
 
+[3.1.1]: https://www.npmjs.com/package/azure-maps-control/v/3.1.1
 [3.1.0]: https://www.npmjs.com/package/azure-maps-control/v/3.1.0
 [3.0.3]: https://www.npmjs.com/package/azure-maps-control/v/3.0.3
 [3.0.2]: https://www.npmjs.com/package/azure-maps-control/v/3.0.2

articles/backup/backup-azure-alternate-dpm-server-troubleshoot.md

@@ -0,0 +1,29 @@
+---
+title: Troubleshoot data recovery from Microsoft Azure Backup Server by using Azure Backup
+description: Learn how to troubleshoot data recovery from Microsoft Azure Backup Server.
+ms.topic: troubleshooting
+ms.date: 01/26/2024
+ms.service: backup
+ms.custom: engagement-fy24
+author: AbhishekMallick-MS
+ms.author: v-abhmallick
+---
+
+# Troubleshoot data recovery from Microsoft Azure Backup Server 
+
+This article provides troubleshooting steps that help you resolve error massages caused during data recovery from Microsoft Azure Backup Server.
+
+## Troubleshoot error messages
+
+| Error Message | Cause | Resolution |
+|:--- |:--- |:--- |
+|This server is not registered to the vault specified by the vault credential. | This error appears when the vault credential file selected doesn't belong to the Recovery Services vault associated with Azure Backup Server on which the recovery is attempted. | Download the vault credential file from the Recovery Services vault to which the Azure Backup Server is registered. |
+|Either the recoverable data isn't available or the selected server isn't a DPM server. | There are no other Azure Backup Servers registered to the Recovery Services vault, or the servers haven't yet uploaded the metadata, or the selected server isn't an Azure Backup Server (using Windows Server or Windows Client). | If there are other Azure Backup Servers registered to the Recovery Services vault, ensure that the latest Azure Backup agent is installed. <br>If there are other Azure Backup Servers registered to the Recovery Services vault, wait for a day after installation to start the recovery process. The nightly job will upload the metadata for all the protected backups to cloud. The data will be available for recovery. |
+|No other DPM server is registered to this vault. | There are no other Azure Backup Servers  that are registered to the vault from which the recovery is being attempted. | If there are other Azure Backup Servers registered to the Recovery Services vault, ensure that the latest Azure Backup agent is installed.<br>If there are other Azure Backup Servers registered to the Recovery Services vault, wait for a day after installation to start the recovery process. The nightly job uploads the metadata for all protected backups to cloud. The data will be available for recovery. |
+|The encryption passphrase provided does not match with passphrase associated with the following server: **\<server name>** | The encryption passphrase used in the process of encrypting the data from the Azure Backup Server’s data that's being recovered doesn't match the encryption passphrase provided. The agent is unable to decrypt the data, and so the recovery fails. | Provide the exact same encryption passphrase associated with the Azure Backup Server whose data is being recovered. |
+
+## Next steps
+
+- [Common questions](backup-azure-vm-backup-faq.yml) about Azure VM backups.
+- [Common questions](backup-azure-file-folder-backup-faq.yml) about the Azure Backup agent.
+- [Recover data from Azure Backup Server](backup-azure-alternate-dpm-server.md).

articles/backup/backup-azure-alternate-dpm-server.md

@@ -1,10 +1,10 @@
 ---
-title: Recover data from an Azure Backup Server
+title: Recover data from an Azure Backup Server by using Azure Backup
 description: Recover the data you've protected to a Recovery Services vault from any Azure Backup Server registered to that vault.
 ms.topic: how-to
-ms.date: 01/24/2023
+ms.date: 01/26/2024
 ms.service: backup
-ms.custom: engagement-fy23
+ms.custom: engagement-fy24
 author: AbhishekMallick-MS
 ms.author: v-abhmallick
 ---
@@ -75,18 +75,11 @@ To recover data from an Azure Backup Server, follow these steps:
 
     ![Screenshot shows how to clear external DPM.](./media/backup-azure-alternate-dpm-server/clear-external-dpm.png)
 
-## Troubleshoot error messages
-
-| Error Message | Cause | Resolution |
-|:--- |:--- |:--- |
-|This server is not registered to the vault specified by the vault credential. | This error appears when the vault credential file selected doesn't belong to the Recovery Services vault associated with Azure Backup Server on which the recovery is attempted. | Download the vault credential file from the Recovery Services vault to which the Azure Backup Server is registered. |
-|Either the recoverable data isn't available or the selected server isn't a DPM server. | There are no other Azure Backup Servers registered to the Recovery Services vault, or the servers haven't yet uploaded the metadata, or the selected server isn't an Azure Backup Server (using Windows Server or Windows Client). | If there are other Azure Backup Servers registered to the Recovery Services vault, ensure that the latest Azure Backup agent is installed. <br>If there are other Azure Backup Servers registered to the Recovery Services vault, wait for a day after installation to start the recovery process. The nightly job will upload the metadata for all the protected backups to cloud. The data will be available for recovery. |
-|No other DPM server is registered to this vault. | There are no other Azure Backup Servers  that are registered to the vault from which the recovery is being attempted. | If there are other Azure Backup Servers registered to the Recovery Services vault, ensure that the latest Azure Backup agent is installed.<br>If there are other Azure Backup Servers registered to the Recovery Services vault, wait for a day after installation to start the recovery process. The nightly job uploads the metadata for all protected backups to cloud. The data will be available for recovery. |
-|The encryption passphrase provided does not match with passphrase associated with the following server: **\<server name>** | The encryption passphrase used in the process of encrypting the data from the Azure Backup Server’s data that's being recovered doesn't match the encryption passphrase provided. The agent is unable to decrypt the data, and so the recovery fails. | Provide the exact same encryption passphrase associated with the Azure Backup Server whose data is being recovered. |
 
 ## Next steps
 
 Read the other FAQs:
 
-* [Common questions](backup-azure-vm-backup-faq.yml) about Azure VM backups
-* [Common questions](backup-azure-file-folder-backup-faq.yml) about the Azure Backup agent
+- [Common questions](backup-azure-vm-backup-faq.yml) about Azure VM backups.
+- [Common questions](backup-azure-file-folder-backup-faq.yml) about the Azure Backup agent.
+- [Troubleshoot error messages](backup-azure-alternate-dpm-server-troubleshoot.md) caused during data recovery from Microsoft Azure Backup Server.

articles/backup/backup-azure-backup-sql.md

@@ -2,11 +2,11 @@
 title: Back up SQL Server to Azure as a DPM workload
 description: An introduction to backing up SQL Server databases by using the Azure Backup service
 ms.topic: how-to
-ms.date: 01/17/2023
+ms.date: 01/26/2024
 ms.service: backup
 author: AbhishekMallick-MS
 ms.author: v-abhmallick
-ms.custom: engagement-fy23
+ms.custom: engagement-fy24
 ---
 
 # Back up SQL Server to Azure as a DPM workload
@@ -15,7 +15,7 @@ This article describes how to back up and restore the SQL Server databases using
 
 Azure Backup helps you to back up SQL Server databases to Azure via an Azure account. If you don't have one, you can create a free account in just a few minutes. For more information, see [Create your Azure free account](https://azure.microsoft.com/pricing/free-trial/).
 
-## SQL Server database backup workflow
+## Backup flow for SQL Server database
 
 To back up a SQL Server database to Azure and to recover it from Azure:
 
@@ -42,16 +42,16 @@ To back up a SQL Server database to Azure and to recover it from Azure:
   * DPM supports multi-site cluster configurations for an instance of SQL Server.
 * When you protect databases that use the Always On feature, DPM has the following limitations:
   * DPM will honor the backup policy for availability groups that's set in SQL Server based on the backup preferences, as follows:
-    * Prefer secondary - Backups should occur on a secondary replica except when the primary replica is the only replica online. If there are multiple secondary replicas available, then the node with the highest backup priority will be selected for backup. IF only the primary replica is available, then the backup should occur on the primary replica.
+    * Prefer secondary - Backups should occur on a secondary replica except when the primary replica is the only replica online. If there are multiple secondary replicas available, then the node with the highest backup priority will be selected for backup. If only the primary replica is available, then the backup should occur on the primary replica.
     * Secondary only - Backup shouldn't be performed on the primary replica. If the primary replica is the only one online, the backup shouldn't occur.
     * Primary - Backups should always occur on the primary replica.
     * Any Replica - Backups can happen on any of the availability replicas in the availability group. The node to be backed up from will be based on the backup priorities for each of the nodes.
-  * Note the following:
-    * Backups can happen from any readable replica -  that is, primary, synchronous secondary, asynchronous secondary.
-    * If any replica is excluded from backup, for example **Exclude Replica** is enabled or is marked as not readable, then that replica won't be selected for backup under any of the options.
-    * If multiple replicas are available and readable, then the node with the highest backup priority will be selected for backup.
-    * If the backup fails on the selected node, then the backup operation fails.
-    * Recovery to the original location isn't supported.
+    >[!Note]
+    >- Backups can happen from any readable replica -  that is, primary, synchronous secondary, asynchronous secondary.
+    >- If any replica is excluded from backup, for example **Exclude Replica** is enabled or is marked as not readable, then that replica won't be selected for backup under any of the options.
+    >- If multiple replicas are available and readable, then the node with the highest backup priority will be selected for backup.
+    >- If the backup fails on the selected node, then the backup operation fails.
+    >- Recovery to the original location isn't supported.
 * SQL Server 2014 or above backup issues:
   * SQL server 2014 added a new feature to create a [database for on-premises SQL Server in Microsoft Azure Blob storage](/sql/relational-databases/databases/sql-server-data-files-in-microsoft-azure). DPM can't be used to protect this configuration.
   * There are some known issues with "Prefer secondary" backup preference for the SQL Always On option. DPM always takes a backup from secondary. If no secondary can be found, then the backup fails.

articles/backup/backup-azure-mars-troubleshoot.md

@@ -2,8 +2,9 @@
 title: Troubleshoot the Azure Backup agent
 description: In this article, learn how to troubleshoot the installation and registration of the Azure Backup agent.
 ms.topic: troubleshooting
-ms.date: 12/05/2022
+ms.date: 05/31/2023
 ms.service: backup
+ms.custom: engagement-fy24
 author: AbhishekMallick-MS
 ms.author: v-abhmallick
 ---
@@ -281,7 +282,7 @@ Unable to find changes in a file. This could be due to various reasons. Please r
 
 ## MARS offline seeding using customer-owned disks (Import/Export) is not working
 
-Azure Import/Export now uses Azure Data Box APIs for offline seeding on customer-owned disks. The Azure portal also list the Import/Export jobs created using the new API under [Azure Data Box jobs](../import-export/storage-import-export-view-drive-status.md?tabs=azure-portal-preview) with the Model column as Import/Export.
+Azure Import/Export now uses Azure Data Box APIs for offline seeding on customer-owned disks. The Azure portal also lists the Import/Export jobs created using the new API under [Azure Data Box jobs](../import-export/storage-import-export-view-drive-status.md?tabs=azure-portal-preview) with the Model column as Import/Export.
 
 MARS agent versions lower than *2.0.9250.0* used the [old Azure Import/Export APIs](/rest/api/storageimportexport/), which will be discontinued after February 28, 2023 and the old MARS agents (version lower than 2.0.9250.0) can't do offline seeding using your own disks. So, we recommend you to use MARS agent 2.0.9250 or higher that uses the new Azure Data Box APIs for offline seeding on your own disks.
 

articles/backup/backup-center-actions.md

@@ -2,8 +2,9 @@
 title: Perform actions using Backup center
 description: This article explains how to perform actions using Backup center
 ms.topic: how-to
-ms.date: 12/08/2022
+ms.date: 03/27/2023
 ms.service: backup
+ms.custom: engagement-fy24
 author: AbhishekMallick-MS
 ms.author: v-abhmallick
 ---

articles/backup/offline-backup-azure-data-box.md

@@ -2,11 +2,11 @@
 title: Offline backup by using Azure Data Box
 description: Learn how you can use Azure Data Box to seed large initial backup data offline from the MARS Agent to a Recovery Services vault. 
 ms.topic: how-to
-ms.date: 1/23/2023
+ms.date: 10/25/2023
 author: AbhishekMallick-MS
 ms.author: v-abhmallick
 ms.service: backup
-ms.custom: engagement-fy23
+ms.custom: engagement-fy24
 ---
 
 # Azure Backup offline backup by using Azure Data Box

articles/backup/toc.yml

@@ -764,7 +764,9 @@
     - name: Archive tier
       href: troubleshoot-archive-tier.md
     - name: Azure Kubernetes Service
-      href: azure-kubernetes-service-backup-troubleshoot.md  
+      href: azure-kubernetes-service-backup-troubleshoot.md
+    - name: Data recovery from Microsoft Azure Backup Server 
+      href: backup-azure-alternate-dpm-server-troubleshoot.md    
 - name: Reference
   items:
   - name: Archived release notes

articles/communication-services/concepts/numbers/phone-number-management-for-australia.md

@@ -20,8 +20,8 @@ Use the below tables to find all the relevant information on number availability
 
 | Number Type | Send SMS             | Receive SMS          | Make Calls           | Receive Calls          |
 | :---------- | :------------------- | :------------------- | :------------------- | :--------------------- |
-| Toll-Free   |-                     | -                    | -      | Public Preview\* |
-| Local   |-                     | -                    | Public Preview      | Public Preview\* |
+| Toll-Free   |-                     | -                    | -      | General Availability\* |
+| Local   |-                     | -                    | General Availability      | General Availability\* |
 | Alphanumeric Sender ID\**       | General Availability                   | -                    | - | - |
 
 \* Please refer to [Inbound calling capabilities page](../telephony/inbound-calling-capabilities.md) for details.

articles/industrial-iot/tutorial-deploy-industrial-iot-platform.md

@@ -99,8 +99,7 @@ The deployment script allows to select which set of components to deploy.
 Other hosting and deployment methods:
 
 - For production deployments that require staging, rollback, scaling, and resilience, the platform can be deployed into [Azure Kubernetes Service (AKS)](/azure/aks/learn/quick-kubernetes-deploy-cli)
-- Deploying Azure Industrial IoT Platform microservices into an existing Kubernetes cluster using [Helm](https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/how-to-deploy-self-hosted-gateway-kubernetes-helm.md).
-- Deploying [Azure Kubernetes Service (AKS) cluster on top of Azure Industrial IoT Platform created by deployment script and adding Azure Industrial IoT components into the cluster](https://github.com/Azure/Industrial-IoT/blob/main/docs/deploy/howto-add-aks-to-ps1.md).
+- Deploying Azure Industrial IoT Platform microservices into an existing Kubernetes cluster using [Helm](/azure/api-management/how-to-deploy-self-hosted-gateway-kubernetes-helm).
 
 References:
 - [Deploying Azure Industrial IoT Platform](/azure/industrial-iot/tutorial-deploy-industrial-iot-platform)