Merge pull request #307818 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: Taojunshen

articles/app-service/overview-inbound-outbound-ips.md

@@ -46,9 +46,9 @@ Run the following command in a local terminal:
 nslookup <app-name>.azurewebsites.net
 ```
 
-## Get a static inbound IP
+## Get a dedicated inbound IP
 
-Sometimes you might want a dedicated, static IP address for your app. To get a static inbound IP address, you need to [secure a custom DNS name with an IP-based certificate binding](./configure-ssl-bindings.md). If you don't actually need TLS functionality to secure your app, you can even upload a self-signed certificate for this binding. In an IP-based TLS binding, the certificate is bound to the IP address itself, so App Service creates a static IP address to make it happen.
+Sometimes you might want a dedicated, static IP address for your app. The default shared inbound IP address is static, but this configuration allows a dedicated inbound IP address unique to your site. To get a dedicated inbound IP address, you need to [secure a custom DNS name with an IP-based certificate binding](./configure-ssl-bindings.md). If you don't actually need TLS functionality to secure your app, you can even upload a self-signed certificate for this binding. In an IP-based TLS binding, the certificate is bound to the IP address itself, so App Service creates a static IP address to make it happen.
 
 ## When outbound IPs change
 

articles/azure-resource-manager/management/tag-support.md

@@ -4069,7 +4069,7 @@ To get the same data as a file of comma-separated values, download [tag-support.
 > [!div class="mx-tableFixed"]
 > | Resource type | Supports tags | Tag in cost report |
 > | ------------- | ----------- | ----------- |
-> | accounts | Yes | Yes |
+> | accounts | Yes | No |
 > | accounts / privateEndpointConnections | No | No |
 > | accounts / privateLinkResources | No | No |
 

articles/dev-box/includes/note-windows-365-announcement.md

@@ -7,11 +7,11 @@ ms.service: dev-box
 ---
 
 > [!IMPORTANT]
-> **Microsoft Dev Box capabilities are coming to Windows 365**
+> **Microsoft Dev Box is evolving into a unified offering within Windows 365**
 >
-> Starting November 1, 2025, Microsoft Dev Box no longer accepts new customers as we integrate Dev Box capabilities into Windows 365. 
+> Starting November 1, 2025, the following changes will take place: 
 >
-> - **Existing customers:** Continue using the service as normal. No action is required.
-> - **New customers:** If you previously evaluated or tested Dev Box and need to onboard after November 1, 2025, reach out to your Microsoft account team.
+> - **Existing customers:**  Continue using the service as normal. No immediate action is required. If you have evaluated or tested Dev Box and need to onboard additional tenants after November 1, 2025, submit a request through Azure Support to get your new tenants allowlisted.
+> - **Net New customers:** Microsoft Dev Box stops accepting net new customers directly. As features are integrated into Windows 365 and become publicly available, customers interested in using them should contact their Microsoft account team.
 >
 > For more information, see [Microsoft Dev Box capabilities are coming to Windows 365](../dev-box-windows-365-announcement.md).

articles/service-bus-messaging/batch-delete.md

@@ -54,6 +54,17 @@ When using Azure SDKs to perform these operations, the beforeEnqueueTime paramet
 >[!NOTE]
 > The purge operation could lead to increased CPU usage as it involves multiple API calls. During purge, locked messages are not eligible for removal and will remain in the entity.
 
+## Quotas
+
+To ensure predictable performance across tiers, Azure Service Bus offers tier-based limits for the maximum number of messages that can be deleted in a single batch delete request:
+
+| Tier | Maximum batch size per request |
+| --- | --- |
+| Standard | 500 messages |
+| Premium  | 4,000 messages |
+
+These limits apply to all batch delete operations initiated via SDKs, REST APIs, and Service Bus Explorer.
+
 
 ## Next steps
 

articles/service-bus-messaging/service-bus-troubleshooting-guide.md

@@ -14,7 +14,7 @@ This article provides troubleshooting tips and recommendations for a few issues
 ## Resource health
 The unhealthy period marked on the **Resource health** page of your Service Bus namespace in the Azure portal might be longer by a few minutes than the actual period. For example, the page might indicate that the namespace is unhealthy for 5-6 minutes, while the actual unhealthy period was only 1-2 minutes. 
 
-This behavior is due to the alert system's evaluation mechanism, which uses a 3-minute evaluation interval combined with a 5-minute lookback window. The lookback window is used to ensure that there are no errors for atleast 5 minutes before considering the namespace healthy. In the above example, the namespace got healthy in a minute or two but the next evaluation happened was atleast 5 minutes (lookback window) after the namespace became healthy. 
+This behavior is due to the alert system's evaluation mechanism, which uses a 3-minute evaluation interval combined with a 5-minute lookback window. The lookback window is used to ensure that there are no errors for at least 5 minutes before considering the namespace healthy. In the above example, the namespace got healthy in a minute or two but the next evaluation happened was at least 5 minutes (lookback window) after the namespace became healthy. 
 
 
 ## Connectivity issues