Merge pull request #297055 from MicrosoftDocs/main

3/26/2025 AM Publish

Author: Taojunshen

articles/app-service/configure-authentication-provider-twitter.md

@@ -41,7 +41,7 @@ To complete the procedure in this article, you need an X account that has a veri
     The secret will be stored as a slot-sticky [application setting](./configure-common.md#configure-app-settings) named `TWITTER_PROVIDER_AUTHENTICATION_SECRET`. You can update that setting later to use [Key Vault references](./app-service-key-vault-references.md) if you wish to manage the secret in Azure Key Vault.
 
 1. If this is the first identity provider configured for the application, you will also be prompted with an **App Service authentication settings** section. Otherwise, you may move on to the next step.
-    
+
     These options determine how your application responds to unauthenticated requests, and the default selections will redirect all requests to log in with this new provider. You can change customize this behavior now or adjust these settings later from the main **Authentication** screen by choosing **Edit** next to **Authentication settings**. To learn more about these options, see [Authentication flow](overview-authentication-authorization.md#authentication-flow).
 
 1. Click **Add**.
@@ -57,4 +57,3 @@ You're now ready to use X for authentication in your app. The provider will be l
 [X Developers]: https://go.microsoft.com/fwlink/p/?LinkId=268300
 [x.com]: https://go.microsoft.com/fwlink/p/?LinkID=268287
 [Azure portal]: https://portal.azure.com/
-[xamarin]: ../app-services-mobile-app-xamarin-ios-get-started-users.md

articles/azure-functions/functions-bindings-notification-hubs.md

@@ -175,15 +175,15 @@ public static async Task Run(string myQueueItem, IAsyncCollector<Notification> n
 {
     log.Info($"C# Queue trigger function processed: {myQueueItem}");
 
-    // In this example, the queue item is a new user to be processed in the form of a JSON string with 
+    // In this example, the queue item is a new user to be processed in the form of a JSON string with
     // a "name" value.
     //
     // The JSON format for a native Apple Push Notification Service (APNS) notification is:
     // { "aps": { "alert": "notification message" }}  
 
     log.LogInformation($"Sending APNS notification of a new user");    
     dynamic user = JsonConvert.DeserializeObject(myQueueItem);    
-    string apnsNotificationPayload = "{\"aps\": {\"alert\": \"A new user wants to be added (" + 
+    string apnsNotificationPayload = "{\"aps\": {\"alert\": \"A new user wants to be added (" +
                                         user.name + ")\" }}";
     log.LogInformation($"{apnsNotificationPayload}");
     await notification.AddAsync(new AppleNotification(apnsNotificationPayload));        
@@ -206,7 +206,7 @@ public static async Task Run(string myQueueItem, IAsyncCollector<Notification> n
 {
     log.Info($"C# Queue trigger function processed: {myQueueItem}");
 
-    // In this example, the queue item is a new user to be processed in the form of a JSON string with 
+    // In this example, the queue item is a new user to be processed in the form of a JSON string with
     // a "name" value.
     //
     // The XML format for a native WNS toast notification is ...
@@ -223,8 +223,8 @@ public static async Task Run(string myQueueItem, IAsyncCollector<Notification> n
     dynamic user = JsonConvert.DeserializeObject(myQueueItem);    
     string wnsNotificationPayload = "<?xml version=\"1.0\" encoding=\"utf-8\"?>" +
                                     "<toast><visual><binding template=\"ToastText01\">" +
-                                        "<text id=\"1\">" + 
-                                            "A new user wants to be added (" + user.name + ")" + 
+                                        "<text id=\"1\">" +
+                                            "A new user wants to be added (" + user.name + ")" +
                                         "</text>" +
                                     "</binding></visual></toast>";
 
@@ -251,7 +251,7 @@ The following table lists the binding configuration properties that you set in t
 |**tagExpression** |**TagExpression** | Tag expressions allow you to specify that notifications be delivered to a set of devices that are registered to receive notifications matching the tag expression. For more information, see [Routing and tag expressions](../notification-hubs/notification-hubs-tags-segment-push-message.md). |
 |**hubName** | **HubName** | The name of the notification hub resource in the Azure portal. |
 |**connection** | **ConnectionStringSetting** | The name of an app setting that contains a Notification Hubs connection string. Set the connection string to the *DefaultFullSharedAccessSignature* value for your notification hub. For more information, see [Connection string setup](#connection-string-setup). |
-|**platform** | **Platform** | The platform property indicates the client platform your notification targets. By default, if the platform property is omitted from the output binding, template notifications can be used to target any platform configured on the Azure Notification Hub. For more information about using templates to send cross-platform notifications with an Azure Notification Hub, see [Notification Hubs templates](../notification-hubs/notification-hubs-templates-cross-platform-push-messages.md). When **platform** is set, it must be one of the following values: <ul><li><code>apns</code>: Apple Push Notification Service. For more information on configuring the notification hub for APNS and receiving the notification in a client app, see [Send push notifications to iOS with Azure Notification Hubs](../notification-hubs/xamarin-notification-hubs-ios-push-notification-apns-get-started.md).</li><li><code>adm</code>: [Amazon Device Messaging](https://developer.amazon.com/device-messaging). For more information on configuring the notification hub for Azure Deployment Manager (ADM) and receiving the notification in a Kindle app, see [Send push notifications to Android devices using Firebase SDK](../notification-hubs/notification-hubs-android-push-notification-google-fcm-get-started.md).</li><li><code>wns</code>: [Windows Push Notification Services](/windows/uwp/design/shell/tiles-and-notifications/windows-push-notification-services--wns--overview) targeting Windows platforms. WNS also supports Windows Phone 8.1 and later. For more information, see [Send notifications to Universal Windows Platform apps using Azure Notification Hubs](../notification-hubs/notification-hubs-windows-store-dotnet-get-started-wns-push-notification.md).</li><li><code>mpns</code>: [Microsoft Push Notification Service](/previous-versions/windows/apps/ff402558(v=vs.105)). This platform supports Windows Phone 8 and earlier Windows Phone platforms. For more information, see [Send notifications to Universal Windows Platform apps using Azure Notification Hubs](../notification-hubs/notification-hubs-windows-mobile-push-notifications-mpns.md).</li></ul> |
+|**platform** | **Platform** | The platform property indicates the client platform your notification targets. By default, if the platform property is omitted from the output binding, template notifications can be used to target any platform configured on the Azure Notification Hub. For more information about using templates to send cross-platform notifications with an Azure Notification Hub, see [Notification Hubs templates](../notification-hubs/notification-hubs-templates-cross-platform-push-messages.md). When **platform** is set, it must be one of the following values: <ul><li><code>apns</code>: Apple Push Notification Service. For more information on configuring the notification hub for APNS and receiving the notification in a client app, see [Send push notifications to .NET MAUI apps using Azure Notification Hubs via a backend service](/dotnet/maui/data-cloud/push-notifications).</li><li><code>adm</code>: [Amazon Device Messaging](https://developer.amazon.com/device-messaging). For more information on configuring the notification hub for Azure Deployment Manager (ADM) and receiving the notification in a Kindle app, see [Send push notifications to Android devices using Firebase SDK](../notification-hubs/notification-hubs-android-push-notification-google-fcm-get-started.md).</li><li><code>wns</code>: [Windows Push Notification Services](/windows/uwp/design/shell/tiles-and-notifications/windows-push-notification-services--wns--overview) targeting Windows platforms. WNS also supports Windows Phone 8.1 and later. For more information, see [Send notifications to Universal Windows Platform apps using Azure Notification Hubs](../notification-hubs/notification-hubs-windows-store-dotnet-get-started-wns-push-notification.md).</li><li><code>mpns</code>: [Microsoft Push Notification Service](/previous-versions/windows/apps/ff402558(v=vs.105)). This platform supports Windows Phone 8 and earlier Windows Phone platforms. For more information, see [Send notifications to Universal Windows Platform apps using Azure Notification Hubs](../notification-hubs/notification-hubs-windows-mobile-push-notifications-mpns.md).</li></ul> |
 
 [!INCLUDE [app settings to local.settings.json](../../includes/functions-app-settings-local.md)]
 
@@ -278,10 +278,10 @@ Here's an example of a Notification Hubs binding in a *function.json* file:
 
 ### Connection string setup
 
-To use a notification hub output binding, you must configure the connection string for the hub. 
+To use a notification hub output binding, you must configure the connection string for the hub.
 
 > [!IMPORTANT]
-> The Notification Hubs binding doesn't support Microsoft Entra authentication and managed identities. You can use Azure Key Vault to centrally manage your notification hub connection string and help with key rotation. To learn more, see [Manage Connections](./manage-connections.md). 
+> The Notification Hubs binding doesn't support Microsoft Entra authentication and managed identities. You can use Azure Key Vault to centrally manage your notification hub connection string and help with key rotation. To learn more, see [Manage Connections](./manage-connections.md).
 
 You can select an existing notification hub or create a new one from the **Integrate** tab in the Azure portal. You can also configure the connection string manually.
 

articles/azure-resource-manager/troubleshooting/error-storage-account-name.md

@@ -3,7 +3,7 @@ title: Resolve errors for storage account names
 description: Describes how to resolve errors for Azure storage account names that can occur during deployment with a Bicep file or Azure Resource Manager template (ARM template).
 ms.topic: troubleshooting
 ms.custom: devx-track-arm-template, devx-track-bicep
-ms.date: 06/20/2024
+ms.date: 03/26/2025
 ---
 
 # Resolve errors for storage account names
@@ -58,8 +58,9 @@ There are two main causes for this error.
 ## Cause 1
 
 The storage account name uses invalid characters or is a duplicate name. Storage account names must meet the following criteria:
-   - Length between 3 and 24 characters with only lowercase letters and numbers.
-   - Must be globally unique across Azure. Storage account names can't be duplicated in Azure.
+
+- Length between 3 and 24 characters with only lowercase letters and numbers.
+- Must be globally unique across Azure. Storage account names can't be duplicated in Azure.
 
 ## Solution 1
 
@@ -130,13 +131,14 @@ name: '${storageNamePrefix}${uniqueString(resourceGroup().id)}'
 "name": "[concat(parameters('storageNamePrefix'), uniquestring(resourceGroup().id))]"
 ```
 
+---
+
 ## Cause 2
 
 The storage account was recently deleted.
-   - If a request to create the storage account comes from a different subscription and tenant than where it was previously located, it will be denied for security purposes as described here, [Prevent dangling DNS entries and avoid subdomain takeover](/azure/security/fundamentals/subdomain-takeover). 
+
+If a request to create the storage account comes from a different subscription and tenant than where it was previously located, it is denied for security purposes as described here, [Prevent dangling DNS entries and avoid subdomain takeover](/azure/security/fundamentals/subdomain-takeover).
 
 ## Solution 2
 
-[Create a Support Request](/azure/azure-portal/supportability/how-to-create-azure-support-request#create-a-support-request****) and choose **Create new storage account** for the problem type, and **Failure(s) during new account creation** for the Problem subtype. Please make sure to include the name of the storage account and the approximate time when account creation failed.
-
----
+[Create a Support Request](/azure/azure-portal/supportability/how-to-create-azure-support-request#create-a-support-request****) and choose **Create new storage account** for the problem type, and **Failure(s) during new account creation** for the Problem subtype. Make sure to include the name of the storage account and the approximate time when account creation failed.

articles/backup/sap-hana-database-restore.md

@@ -2,7 +2,7 @@
 title: Restore SAP HANA databases on Azure VMs
 description: In this article, you'll learn how to restore SAP HANA databases that are running on Azure virtual machines. You can also use Cross Region Restore to restore your databases to a secondary region.
 ms.topic: how-to
-ms.date: 03/26/2024
+ms.date: 03/26/2025
 ms.service: azure-backup
 author: jyothisuri
 ms.author: jsuri
@@ -25,9 +25,9 @@ For information about the supported configurations and scenarios, see the [SAP H
 
 Azure Backup restores SAP HANA databases that are running on Azure VMs. It can:
 
-* Restore them to a specific date or time (to the second) by using log backups. Azure Backup automatically determines the appropriate full backups, differential backups, and chain of log backups that are required to restore based on the selected time.
+* Restore them to a specific date or time (to the second) by using log backups. Azure Backup automatically determines the appropriate full backups, differential backups, and chain of log backups that are required to restore based on the selected time. [Learn more](#restore-to-a-specific-point-in-time).
 
-* Restore them to a specific full or differential backup to restore them to a specific recovery point.
+* Restore them to a specific full or differential backup to restore them to a specific recovery point. [Learn more](#restore-to-a-specific-recovery-point).
 
 ## Prerequisites
 

articles/container-apps/waf-app-gateway.md

@@ -5,13 +5,13 @@ services: container-apps
 author: cachai2
 ms.service: azure-container-apps
 ms.topic:  how-to
-ms.date: 03/31/2023
+ms.date: 03/26/2025
 ms.author: cachai
 ---
 
 # Protect Azure Container Apps with Web Application Firewall on Application Gateway
 
-When you host your apps or microservices in Azure Container Apps, you may not always want to publish them directly to the internet. Instead, you may want to expose them through a reverse proxy.
+When you host your apps or microservices in Azure Container Apps, you might not always want to publish them directly to the internet. Instead, you might want to expose them through a reverse proxy.
 
 A reverse proxy is a service that sits in front of one or more services, intercepting and directing incoming traffic to the appropriate destination.
 
@@ -48,9 +48,13 @@ Use the following steps to retrieve the values of the **default domain** and the
 
 ## Create and configure an Azure Private DNS zone
 
-1. On the Azure portal menu or the *Home* page, select **Create a resource**.
+To create and configure an Azure Private DNS zone, perform the following steps:
 
-1. Search for *Private DNS Zone*, and select **Private DNS Zone** from the search results.
+1. Go to the Azure portal.
+
+1. In the search bar, enter **Private DNS Zone**.
+
+1. Select **Private DNS Zone** from the search results.
 
 1. Select the **Create** button.
 
@@ -110,8 +114,20 @@ Use the following steps to retrieve the values of the **default domain** and the
 
 ## Create and configure Azure Application Gateway
 
+To create and configure an Azure Application Gateway, perform the following steps:
+
+1. Go to the Azure portal.
+
+1. In the search bar, enter **Application Gateway**.
+
+1. Select **Application Gateway** from the search results.
+
+Now, enter the required details under the *Basics* tab, *Frontends* tab, *Backends* tab, and *Configuration* tab.
+
 ### Basics tab
 
+Perform the following steps:
+
 1. Enter the following values in the *Project details* section.
 
     | Setting | Action |
@@ -151,6 +167,8 @@ Use the following steps to retrieve the values of the **default domain** and the
 
 ### Frontends tab
 
+Perform the following steps:
+
 1. On the *Frontends* tab, enter the following values:
 
     | Setting | Action |
@@ -174,7 +192,9 @@ The backend pool is used to route requests to the appropriate backend servers. B
 - Fully qualified domain names (FQDN)
 - Multi-tenant back-ends like Azure App Service and Container Apps
 
-In this example, you create a backend pool that targets your container app.
+In this example, you create a backend pool that targets your container app. 
+
+To create a backend pool, perform the following steps:
 
 1. Select **Add a backend pool**.
 
@@ -197,7 +217,9 @@ In this example, you create a backend pool that targets your container app.
 
 ### Configuration tab
 
-On the *Configuration* tab, you connect the frontend and backend pool you created using a routing rule.
+On the *Configuration* tab, you connect the frontend and backend pool you created using a routing rule. 
+
+To connect the frontend and backend pool, perform the following steps:
 
 1. Select **Add a routing rule**. Enter the following values:
 
@@ -266,7 +288,7 @@ On the *Configuration* tab, you connect the frontend and backend pool you create
 
 ## Add private link to your Application Gateway
 
-You can establish a secured connection to internal-only container app environments by leveraging private link, as it allows your Application Gateway to communicate with your Container App on the backend through the virtual network.
+You can establish a secured connection to internal-only container app environments using private link. Private link allows your Application Gateway to communicate with your Container App on the backend through the virtual network.
 
 1. Once the Application Gateway is created, select **Go to resource**.
 

articles/cost-management-billing/manage/discover-cloud-footprint.md

@@ -3,7 +3,7 @@ title: Discover your Microsoft cloud footprint FAQ
 description: This article helps to answer frequently asked questions that customers have about their Microsoft cloud footprint.
 author: bandersmsft
 ms.author: banders
-ms.date: 01/08/2025
+ms.date: 03/26/2025
 ms.topic: concept-article
 ms.service: cost-management-billing
 ms.subservice: cost-management

articles/ddos-protection/alerts.md

@@ -5,7 +5,7 @@ services: ddos-protection
 author: AbdullahBell
 ms.service: azure-ddos-protection
 ms.topic: tutorial
-ms.date: 02/10/2025
+ms.date: 03/17/2025
 ms.author: abell
 ---
 

articles/ddos-protection/ddos-diagnostic-alert-templates.md

@@ -5,7 +5,7 @@ services: ddos-protection
 author: AbdullahBell
 ms.service: azure-ddos-protection
 ms.topic: tutorial
-ms.date: 02/10/2025
+ms.date: 03/17/2025
 ms.author: abell
 ---