Merge pull request #310087 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.md

@@ -25,7 +25,7 @@ Whether you're a student, a small business, a startup, or an enterprise, App Ser
 
 ### Students
 
-- **Free access**: In addition to the widely available [free tier](https://azure.microsoft.com/pricing/details/app-service/), students can take advantage of the [Azure for Students Starter](https://azure.microsoft.com/pricing/offers/ms-azr-0144p) program.
+- **Free access**: In addition to the widely available [free tier](https://azure.microsoft.com/pricing/purchase-options/azure-account), students can take advantage of the [Azure for Students Starter](https://azure.microsoft.com/pricing/offers/ms-azr-0144p) program.
 - **IDE support**: Purpose-built deployment tools are available for Visual Studio, Visual Studio Code, IntelliJ, and Eclipse.
 - **Easy to use**: Run your apps without needing experience in infrastructure management.
 - **Learning Resources**: Plenty of tutorials and guides to help you get started.

articles/container-apps/container-apps-extension-release-notes.md

@@ -198,3 +198,28 @@ ms.custom:
 - Supported dynamic concurrency for workflow trigger
 - Added RabbitMQ Keda translation
 - Fixed issues for OpenShift cluster
+
+## v1.50.1 (December 2025)
+
+- Updated base image to Azure Linux 3.0.
+- Upgraded EasyAuth to version 1.12.0.
+- Upgraded Dapr to 1.13.6-msft.6.
+- Updated KEDA to 2.17.2-msft.1.
+- Enhanced system sidecar and updated k8s.io/kubernetes to address security vulnerabilities.
+- Upgraded Geneva MDM and MDSD image versions.
+- Increased memory limits for the KEDA operator.
+- Increased Envoy resources limits.
+- Updated Auth container resource limits.
+- Set `maxInactiveRevisionsDefault` to 200.
+- Adopted KEDA-specific annotation for pausing event-triggered jobs.
+- Fixed `useMonitor` logic in Timer trigger KEDA SyncTrigger.
+- Added readiness and liveness probe configurations for the Dapr injector.
+- Implemented logic to restart the event processor if no event has been updated in the last 5 minutes.
+- Enhanced Envoy controller for app routes.
+- Added validation for SMB changes.
+- Enabled named job execution.
+- Enabled IP restrictions for HTTP routes.
+- Added `containerName` for CPU/memory autoscaling.
+- Increased localproxy sidecar readiness probe failure threshold.
+- Improved lifecycle and history management for labels mode.
+- Prevented creation of new revisions or replicasets when only the `TargetLabel` changes.

articles/container-apps/environment-custom-dns-suffix.md

@@ -22,9 +22,9 @@ Azure Container Apps environment provides a default DNS suffix in the format `<U
 
 1. Go to your Container Apps environment in the [Azure portal](https://portal.azure.com)
 
-1. Under the *Settings* section, select **Custom DNS suffix**.
+1. Under the *Settings* section, select **Networking** and then click on **Custom DNS Suffix**.
 
-1. In **DNS suffix**, enter the custom DNS suffix for the environment.
+1. In **Custom DNS suffix**, enter the custom DNS suffix for the environment.
 
     For example, if you enter `example.com`, the container app domain names are in the format `<APP_NAME>.example.com`.
 

articles/iot-operations/includes/deploy-connectors-simple.md

@@ -13,7 +13,7 @@ All the connectors can publish captured data to the MQTT broker.
 
 To add a connector template instance to your Azure IoT Operations instance:
 
-1. In the Azure portal, go to your Azure IoT Operations instance, select **Connector templates**, and then select **Add connector template instances**:
+1. In the Azure portal, go to your Azure IoT Operations instance, select **Connector templates**, and then select **Create a connector template**:
 
     :::image type="content" source="media/deploy-connectors-simple/portal-add-connector-template.png" alt-text="Screenshot of Azure portal that shows how to add a connector template instance." lightbox="media/deploy-connectors-simple/portal-add-connector-template.png":::
 

articles/static-web-apps/database-overview.md

@@ -10,6 +10,10 @@ ms.date: 03/03/2023
 
 # Connecting to a database with Azure Static Web Apps (preview)
 
+> [!IMPORTANT]
+> Retirement notice: Database Connections for Static Web Apps ends November 30, 2025. Migrate now to avoid disruption.
+
+
 The Azure Static Web Apps database connection feature allows you to access a database from your static web app without writing custom server-side code.
 
 Once you create a connection between your web application and database, you can manipulate data with full support for CRUD operations, built-in authorization, and relationships.

includes/storage-account-key-note-include.md

@@ -15,7 +15,7 @@ ms.custom: "include file", engagement-fy23
 Storage account access keys provide full access to the storage account data and the ability to generate SAS tokens. Always be careful to protect your access keys. Use Azure Key Vault to manage and rotate your keys securely. Access to the shared key grants a user full access to a storage account’s data. Access to shared keys should be carefully limited and monitored. Use user delegation SAS tokens with limited scope of access in scenarios where Microsoft Entra ID based authorization can't be used. Avoid hard-coding access keys or saving them anywhere in plain text that is accessible to others. Rotate your keys if you believe they might have been compromised.
 
 > [!IMPORTANT]
-> To prevent users from accessing data in your storage account with Shared Key, you can disallow Shared Key authorization for the storage account. Granular access to data with least privileges necessary is recommended as a security best practice. Microsoft Entra ID based authorization using managed identities should be used for scenarios that support OAuth. Kerberos or SMTP should be used for Azure Files over SMB. For Azure Files over REST, SAS tokens can be used. Shared key access should be disabled if not required to prevent its inadvertent use. For more information, see [Prevent Shared Key authorization for an Azure Storage account](../articles/storage/common/shared-key-authorization-prevent.md).
+> To prevent users from accessing data in your storage account with Shared Key, you can disallow Shared Key authorization for the storage account. Granular access to data with least privileges necessary is recommended as a security best practice. Microsoft Entra ID based authorization using managed identities should be used for scenarios that support OAuth. Kerberos should be used for Azure Files over SMB. For Azure Files over REST, SAS tokens can be used. Shared key access should be disabled if not required to prevent its inadvertent use. For more information, see [Prevent Shared Key authorization for an Azure Storage account](../articles/storage/common/shared-key-authorization-prevent.md).
 >
 > To protect an Azure Storage account with Microsoft Entra Conditional Access policies, you must disallow Shared Key authorization for the storage account.
 >