Merge pull request #291073 from MicrosoftDocs/main

Publish to live, Tuesday 4 AM PST, 11/26

Author: ttorble

articles/app-service/configure-basic-auth-disable.md

@@ -68,7 +68,7 @@ The following table shows how various deployment methods behave when basic authe
 | Visual Studio deployment | Doesn't work. |
 | [FTP](deploy-ftp.md) | Doesn't work. |
 | [Local Git](deploy-local-git.md) | Doesn't work. |
-| Azure CLI | In Azure CLI 2.48.1 or higher, the following commands fall back to Microsoft Entra authentication:<br/>- [az webapp up](/cli/azure/webapp#az-webapp-up)<br/>- [az webapp deploy](/cli/azure/webapp#az-webapp-deploy)<br/>- [az webapp deployment source config-zip](/cli/azure/webapp/deployment/source#az-webapp-deployment-source-config-zip)<br/>- [az webapp log deployment show](/cli/azure/webapp/log/deployment#az-webapp-log-deployment-show)<br/>- [az webapp log deployment list](/cli/azure/webapp/log/deployment#az-webapp-log-deployment-list)<br/>- [az webapp log download](/cli/azure/webapp/log#az-webapp-log-download)<br/>- [az webapp log tail](/cli/azure/webapp/log#az-webapp-log-tail)<br/>- [az webapp browse](/cli/azure/webapp#az-webapp-browse)<br/>- [az webapp create-remote-connection](/cli/azure/webapp#az-webapp-create-remote-connection)<br/>- [az webapp ssh](/cli/azure/webapp#az-webapp-ssh)<br/>- [az functionapp deploy](/cli/azure/functionapp#az-functionapp-deploy)<br/>- [az functionapp log deployment list](/cli/azure/functionapp/log/deployment#az-functionapp-log-deployment-list)<br/>- [az functionapp log deployment show](/cli/azure/functionapp/log/deployment#az-functionapp-log-deployment-show)<br/>- [az functionapp deployment source config-zip](/cli/azure/functionapp/deployment/source#az-functionapp-deployment-source-config-zip) |
+| Azure CLI | In Azure CLI 2.48.1 or higher, the following commands fall back to Microsoft Entra authentication:<br/>- [az webapp up](/cli/azure/webapp#az-webapp-up)<br/>- [az webapp deploy](/cli/azure/webapp#az-webapp-deploy)<br/>- [az webapp log deployment show](/cli/azure/webapp/log/deployment#az-webapp-log-deployment-show)<br/>- [az webapp log deployment list](/cli/azure/webapp/log/deployment#az-webapp-log-deployment-list)<br/>- [az webapp log download](/cli/azure/webapp/log#az-webapp-log-download)<br/>- [az webapp log tail](/cli/azure/webapp/log#az-webapp-log-tail)<br/>- [az webapp browse](/cli/azure/webapp#az-webapp-browse)<br/>- [az webapp create-remote-connection](/cli/azure/webapp#az-webapp-create-remote-connection)<br/>- [az webapp ssh](/cli/azure/webapp#az-webapp-ssh)<br/>- [az functionapp deploy](/cli/azure/functionapp#az-functionapp-deploy)<br/>- [az functionapp log deployment list](/cli/azure/functionapp/log/deployment#az-functionapp-log-deployment-list)<br/>- [az functionapp log deployment show](/cli/azure/functionapp/log/deployment#az-functionapp-log-deployment-show)<br/>- [az functionapp deployment source config-zip](/cli/azure/functionapp/deployment/source#az-functionapp-deployment-source-config-zip) |
 | [Maven plugin](https://github.com/microsoft/azure-maven-plugins) or [Gradle plugin](https://github.com/microsoft/azure-gradle-plugins) | Works. |
 | [GitHub with App Service Build Service](deploy-continuous-deployment.md?tabs=github) | Doesn't work. |
 | [GitHub Actions](deploy-continuous-deployment.md?tabs=github) | - An existing GitHub Actions workflow that uses **basic authentication** can't authenticate. In the Deployment Center, disconnect the existing GitHub configuration and create a new GitHub Actions configuration with the **user-assigned identity** option instead. <br/> - If the existing GitHub Actions deployment is [manually configured](deploy-github-actions.md), try using a service principal or OpenID Connect instead. <br/> - For new GitHub Actions configuration in the Deployment Center, use the **user-assigned identity** option. |

articles/app-service/deploy-authentication-types.md

@@ -16,7 +16,7 @@ Azure App Service lets you deploy your web application code and configuration by
 
 |Deployment method|Authentication  |Reference Documents |
 |:----|:----|:----|
-|Azure CLI |Microsoft Entra ID | In Azure CLI, version 2.48.1 or higher, the following commands have been modified to use Microsoft Entra if basic authentication is turned off for your web app or function app:<br/>- [az webapp up](/cli/azure/webapp#az-webapp-up)<br/>- [az webapp deploy](/cli/azure/webapp#az-webapp-deploy)<br/>- [az webapp deployment source config-zip](/cli/azure/webapp/deployment/source#az-webapp-deployment-source-config-zip)<br/>- [az webapp log deployment show](/cli/azure/webapp/log/deployment#az-webapp-log-deployment-show)<br/>- [az webapp log deployment list](/cli/azure/webapp/log/deployment#az-webapp-log-deployment-list)<br/>- [az webapp log download](/cli/azure/webapp/log#az-webapp-log-download)<br/>- [az webapp log tail](/cli/azure/webapp/log#az-webapp-log-tail)<br/>- [az webapp browse](/cli/azure/webapp#az-webapp-browse)<br/>- [az webapp create-remote-connection](/cli/azure/webapp#az-webapp-create-remote-connection)<br/>- [az webapp ssh](/cli/azure/webapp#az-webapp-ssh)<br/>- [az functionapp deploy](/cli/azure/functionapp#az-functionapp-deploy)<br/>- [az functionapp log deployment list](/cli/azure/functionapp/log/deployment#az-functionapp-log-deployment-list)<br/>- [az functionapp log deployment show](/cli/azure/functionapp/log/deployment#az-functionapp-log-deployment-show)<br/>- [az functionapp deployment source config-zip](/cli/azure/functionapp/deployment/source#az-functionapp-deployment-source-config-zip)<br/>For more information, see [az appservice](/cli/azure/appservice) and [az webapp](/cli/azure/webapp). |
+|Azure CLI |Microsoft Entra ID | In Azure CLI, version 2.48.1 or higher, the following commands have been modified to use Microsoft Entra if basic authentication is turned off for your web app or function app:<br/>- [az webapp up](/cli/azure/webapp#az-webapp-up)<br/>- [az webapp deploy](/cli/azure/webapp#az-webapp-deploy)<br/>- [az webapp log deployment show](/cli/azure/webapp/log/deployment#az-webapp-log-deployment-show)<br/>- [az webapp log deployment list](/cli/azure/webapp/log/deployment#az-webapp-log-deployment-list)<br/>- [az webapp log download](/cli/azure/webapp/log#az-webapp-log-download)<br/>- [az webapp log tail](/cli/azure/webapp/log#az-webapp-log-tail)<br/>- [az webapp browse](/cli/azure/webapp#az-webapp-browse)<br/>- [az webapp create-remote-connection](/cli/azure/webapp#az-webapp-create-remote-connection)<br/>- [az webapp ssh](/cli/azure/webapp#az-webapp-ssh)<br/>- [az functionapp deploy](/cli/azure/functionapp#az-functionapp-deploy)<br/>- [az functionapp log deployment list](/cli/azure/functionapp/log/deployment#az-functionapp-log-deployment-list)<br/>- [az functionapp log deployment show](/cli/azure/functionapp/log/deployment#az-functionapp-log-deployment-show)<br/>- [az functionapp deployment source config-zip](/cli/azure/functionapp/deployment/source#az-functionapp-deployment-source-config-zip)<br/>For more information, see [az appservice](/cli/azure/appservice) and [az webapp](/cli/azure/webapp). |
 |Azure PowerShell |Microsoft Entra | In Azure PowerShell, version 9.7.1 or above, Microsoft Entra is available for App Service. For more information, see [PowerShell samples for Azure App Service](samples-powershell.md). |
 |SCM/Kudu/OneDeploy REST endpoint |Basic authentication<br/>Microsoft Entra |[Deploy files to App Service](deploy-zip.md) |
 |Kudu UI |Basic authentication<br/>Microsoft Entra |[Deploy files to App Service](deploy-zip.md)|

articles/app-service/deploy-run-package.md

@@ -42,7 +42,7 @@ az webapp config appsettings set --resource-group <group-name> --name <app-name>
 
 ## Run the package
 
-The easiest way to run a package in your App Service is with the Azure CLI [az webapp deployment source config-zip](/cli/azure/webapp/deployment/source#az-webapp-deployment-source-config-zip) command. For example:
+The easiest way to run a package in your App Service is with the Azure CLI [az webapp deploy](/cli/azure/webapp#az-webapp-deploy) command. For example:
 
 ```azurecli-interactive
 az webapp deploy --resource-group <group-name> --name <app-name> --src-path <filename>.zip

articles/app-service/quickstart-arc.md

@@ -75,7 +75,7 @@ git clone https://github.com/Azure-Samples/nodejs-docs-hello-world
 cd nodejs-docs-hello-world
 zip -r package.zip .
 az webapp config appsettings set --resource-group myResourceGroup --name <app-name> --settings SCM_DO_BUILD_DURING_DEPLOYMENT=true
-az webapp deployment source config-zip --resource-group myResourceGroup --name <app-name> --src package.zip
+az webapp deploy --resource-group myResourceGroup --name <app-name> --src-path package.zip
 ```
 
 ## 5. Get diagnostic logs using Log Analytics

articles/app-service/tutorial-connect-msi-key-vault-php.md

@@ -32,7 +32,7 @@ appName=<app-name>
 
 az appservice plan create --resource-group $groupName --name $appName --sku FREE --location $region
 az webapp create --resource-group $groupName --plan $appName --name $appName
-az webapp deployment source config-zip --resource-group $groupName --name $appName --src ./default.zip
+az webapp deploy --resource-group $groupName --name $appName --src-path ./default.zip
 ```
 
 ## Configure secrets as app settings

articles/azure-signalr/signalr-howto-use.md

@@ -154,6 +154,14 @@ You can increase this value to avoid client disconnect.
 - This option defines a function to customize the transports that clients can use to send HTTP requests.
 - Use this options instead of [`HttpConnectionDispatcherOptions.Transports`](/aspnet/core/signalr/configuration?&tabs=dotnet#advanced-http-configuration-options) to configure transports. 
 
+#### `AllowStatefulReconnects`
+
+- Default value is `null`
+- This option enables or disables stateful reconnects for all hubs.
+- If `null`, SDK will read [hub settings](/dotnet/api/microsoft.aspnetcore.http.connections.httpconnectiondispatcheroptions.allowstatefulreconnects).
+- If `true`, Azure SignalR Service will enable stateful reconnects in all of declared hubs. And clients need [enable stateful reconnects in client side](/aspnet/core/signalr/configuration).
+- If `false`, Azure SignalR Service will disable stateful reconnects in all of declared hubs.
+
 ### Sample
 
 You can configure above options like the following sample code.

articles/backup/blob-backup-overview.md

@@ -2,7 +2,7 @@
 title: Overview of Azure Blobs backup
 description: Learn about Azure Blobs backup.
 ms.topic: overview
-ms.date: 07/24/2024
+ms.date: 11/26/2024
 ms.service: azure-backup
 author: AbhishekMallick-MS
 ms.author: v-abhmallick
@@ -104,7 +104,14 @@ You won't incur any management charges or instance fee when using operational ba
 
 # [Vaulted backup](#tab/vaulted-backup)
 
-You will incur backup storage charges or instance fees, and the source side cost ([associated with Object replication](../storage/blobs/object-replication-overview.md#billing)) on the backed-up source account.
+Azure Blobs protected with Azure Backup incur charges as per the [Azure Backup pricing](https://azure.microsoft.com/pricing/details/backup/) that includes:
+
+- **Protected instance fee**: Azure Backup for Blobs charges a protected instance fee per month. The size of data in the protected storage account determines the pricing for each instance. For specific pricing details, go to the [Azure Backup pricing](https://azure.microsoft.com/pricing/details/backup/) and select **Azure Blobs** as the workload type.
+- **Transactions fee**: The transaction fee is calculated based on the **write operations** performed by the Azure Backup service to back up data to the backup storage account. This charge depends on the frequency of writes to the protected storage account.
+- **Backup Storage fee**: This fee is charged based on the restore points stored in the Vault Tier (as per the total data stored in GBs and redundancy type enable on the Backup Vault). Backup storage redundancy is the redundancy you set for the vault used for protecting Azure Blob.
+
+For generating the estimate for your scenario see the [Azure Backup pricing calculator](https://azure.microsoft.com/pricing/calculator/?service=backup).
+
 
 ---
 

articles/communications-gateway/overview.md

@@ -11,6 +11,9 @@ ms.date: 10/22/2024
 
 # What is Azure Communications Gateway?
 
+> [!IMPORTANT]
+> The Azure Communications Gateway service will retire on October 30, 2025. To prevent any service disruption, please transition to another [Microsoft Teams Direct Routing certified Session Border Controller (SBC)](https://learn.microsoft.com/microsoftteams/direct-routing-border-controllers) solution before October 30, 2025.
+
 Azure Communications Gateway provides quick, reliable and secure integration with multiple services for telecommunications operators:
 
 - Microsoft Teams calling through the Operator Connect, Teams Phone Mobile and Microsoft Teams Direct Routing programs

articles/data-factory/connector-deprecation-frequently-asked-questions.md

@@ -67,11 +67,11 @@ There are three key deadlines outlined in our documentation:
 
 ## What should I do if I encounter the feature gaps and errors/ bugs that are preventing me from migrating to the new connectors?
 
-If you encounter any feature gaps while migrating from legacy connectors, please review our connector documentation to check if it’s a known limitation. Additionally, send us an email at **[email protected]** with a description of the feature gap.
+If you encounter any feature gaps while migrating from legacy connectors, please review our connector documentation to check if it’s a known limitation. Additionally, send us an email at **[email protected]** with a description of the feature gap. 
 
 If you encounter any errors or bugs while migrating from legacy connectors, please contact our Microsoft support team and open a support ticket. Be sure to include detailed information about the connector, the error encountered, and your use case.
 
-Our Azure Data Factory team will assist you and ensure a smooth transition to the new connectors.
+Our Azure Data Factory team will assist you and ensure a smooth transition to the new connectors. We invite you to fill out this [form](https://forms.office.com/pages/responsepage.aspx?id=v4j5cvGGr0GRqy180BHbR94fEtK94M9FsNIwB3-nUTtUQTFGMjVFNkNEVkFaTEJQMUVaQlc3TlRDVi4u&route=shorturl) to help us better understand your needs and explore possible solutions.
 
 ## Related content
 

articles/data-factory/connector-deprecation-plan.md

@@ -29,6 +29,7 @@ This article describes future upgrades for some connectors of Azure Data Factory
 | [PostgreSQL (legacy)](connector-postgresql-legacy.md)   | [Link](connector-postgresql.md#upgrade-the-postgresql-linked-service)| End of support announced and new version available |October 31, 2024 | /  | 
 | [ServiceNow (legacy)](connector-servicenow-legacy.md)   | [Link](connector-servicenow.md#upgrade-your-servicenow-linked-service) | End of support announced and new version available | To be determined | / | 
 | [Snowflake (legacy)](connector-snowflake-legacy.md)   | [Link](connector-snowflake.md#upgrade-the-snowflake-linked-service) | End of support announced and new version available | To be determined | /  | 
+| [Vertica (version 1.0)](connector-vertica.md)| [Link](connector-vertica.md#upgrade-the-vertica-version) | End of support announced and new version available | To be determined | /  | 
 | [Azure Database for MariaDB](connector-azure-database-for-mariadb.md) |/ | End of support announced |December 31, 2024 | December 31, 2024 | 
 | [Concur (Preview)](connector-concur.md) |/ | End of support announced | December 31, 2024 | December 31, 2024 | 
 | [Couchbase (Preview)](connector-couchbase.md) |/ | End of support announced | December 31, 2024 | December 31, 2024 | 
@@ -68,6 +69,7 @@ The following legacy connectors or legacy driver versions will be deprecated, bu
 - [Salesforce Service Cloud](connector-salesforce-service-cloud.md#upgrade-the-salesforce-service-cloud-linked-service)
 - [ServiceNow](connector-servicenow.md#upgrade-your-servicenow-linked-service)
 - [Snowflake](connector-snowflake.md#upgrade-the-snowflake-linked-service)
+- [Vertica](connector-vertica.md#upgrade-the-vertica-version)
 
 ## Connectors to be deprecated on December 31, 2024