Merge pull request #293994 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: rmca14

articles/app-service/includes/deploy-intelligent-apps/deploy-intelligent-apps-linux-python-pivot.md

@@ -30,6 +30,10 @@ CMK Error Handling: Improved error handling for operations dependent on customer
 
 The FHIR® server has a limit of 100 items on `include` and `revinclude` searches. A recent update fixed an issue where this limit was not being applied in specific conditions. Customers will receive a warning and truncated results if the limit is exceeded. Details on limits can be found in the [Overview of FHIR search](./fhir/overview-of-search.md#search-result-parameters). To manage this, use the `_count` parameter to reduce the number of returned results. In the short term, we plan to increase the limit to 1000
 
+### Bug Fixes
+
+Billing in Sweden Central region: An issue was discovered where subscriptions in the Sweden Central region were not being billed correctly. We corrected the error, and billing has now been enabled in Sweden Central region. If you were affected by this error, you will not be responsible for any missed charged prior to your January bill.
+
 ## Related content
 
 [Release notes 2021](release-notes-2021.md)

articles/healthcare-apis/release-notes-2025.md

@@ -48,9 +48,9 @@ Service Connector offers the following authentication options:
 | Azure Cosmos DB for NoSQL                     | Yes                              | Yes                            | Yes               | Yes               |
 | Azure Cosmos DB for Table                     | Yes                              | Yes                            | Yes               | Yes               |
 | Azure Database for MySQL single server        | Yes                              | No                             | No                | No                |
-| Azure Database for MySQL flexible server      | Yes                              | No                             | Yes               | No                |
+| Azure Database for MySQL Flexible Server      | Yes                              | No                             | Yes               | No                |
 | Azure Database for PostgreSQL single server   | Yes                              | No                             | Yes               | No                |
-| Azure Database for PostgreSQL flexible server | Yes                              | No                             | Yes               | No                |
+| Azure Database for PostgreSQL Flexible Server | Yes                              | No                             | Yes               | No                |
 | Azure Event Hubs                              | Yes                              | Yes                            | Yes               | Yes               |
 | Azure Files                                   | No                               | No                             | Yes               | No                |
 | Azure Key Vault                               | Yes                              | Yes                            | No                | Yes               |

articles/service-connector/how-to-manage-authentication.md

@@ -50,6 +50,21 @@ Azure Storage Mover is a hybrid service, which continuously introduces new featu
 > [!IMPORTANT]
 > Preview versions of the Storage Mover agent cannot update themselves. You must replace them manually by deploying the [latest available agent](https://aka.ms/StorageMover/agent).
 
+## 2025 January 28
+
+Major refresh release notes for:
+
+- Service version: January 28, 2025
+- Agent version: 3.3.708
+
+### What's new
+
+- Proxy related improvements and bug fixes
+- Security and performance improvements and bug fixes
+- Ability to collect and diagnose SMB mount related issues
+- Adding network diagnostics tools - ping, nslookup
+- Improved Unicode character handling for SMB source
+
 ## 2024 August 30
 
 Major refresh release notes for:

articles/storage-mover/release-notes.md

@@ -55,6 +55,7 @@ These Blob REST APIs aren't supported:
 - [Get Page Ranges](/rest/api/storageservices/get-page-ranges)
 - [Incremental Copy Blob](/rest/api/storageservices/incremental-copy-blob)
 - [Put Page from URL](/rest/api/storageservices/put-page-from-url)
+- [Append Blob Seal](/rest/api/storageservices/append-blob-seal)
 
 Unmanaged VM disks aren't supported in accounts that have a hierarchical namespace. If you want to enable a hierarchical namespace on a storage account, place unmanaged VM disks into a storage account that doesn't have the hierarchical namespace feature enabled.
 

articles/storage/blobs/data-lake-storage-known-issues.md

@@ -55,7 +55,6 @@ The following Blob storage operations support sending customer-provided encrypti
 - [Put Page](/rest/api/storageservices/put-page)
 - [Put Page from URL](/rest/api/storageservices/put-page-from-url)
 - [Append Block](/rest/api/storageservices/append-block)
-- [Set Blob Properties](/rest/api/storageservices/set-blob-properties)
 - [Set Blob Metadata](/rest/api/storageservices/set-blob-metadata)
 - [Get Blob](/rest/api/storageservices/get-blob)
 - [Get Blob Properties](/rest/api/storageservices/get-blob-properties)

articles/storage/blobs/encryption-customer-provided-keys.md

@@ -19,7 +19,7 @@ You can securely connect  to Azure Synapse Studio from your Azure virtual networ
 
 There are two steps to connect to Synapse Studio using private links. First, you must create a private link hubs resource. Second, you must create a private endpoint from your Azure virtual network to this private link hub. You can then use private endpoints to securely communicate with Synapse Studio. You must integrate the private endpoints with your DNS solution, either your on-premises solution or Azure Private DNS. 
 
-## Azure Private Links Hubs and Azure Synapse Studio
+## Azure Private Link Hubs and Azure Synapse Studio
 You can use a single Azure Synapse private link hub resource to privately connect to all your Azure Synapse Analytics workspaces using Azure Synapse Studio. The workspaces do not have to be in the same region as the Azure Synapse Private link hub. The Azure Synapse Private link hub resource can also be used for connections to Synapse workspaces in different subscriptions or Microsoft Entra tenants.
 
 You can create your private link hub by searching for *Synapse private link hubs* in the Azure portal and selecting **Azure Synapse Analytics (private link hubs)** from Services. Follow the steps in the guide for how to [connect to workspace resources from a restricted network](./how-to-connect-to-workspace-from-restricted-network.md) for details. Certain URLs must be accessible from the client browser after enabling Azure Synapse private link hub. For more information, see [Connect to workspace resources from a restricted network](how-to-connect-to-workspace-from-restricted-network.md).
@@ -29,7 +29,7 @@ You can create your private link hub by searching for *Synapse private link hubs
 >[!NOTE]
 >Private link hubs are intended for securely loading the static content Synapse Studio over private links. You must create **separate, private endpoints** to the  resources you wish to connect to within the workspace, such as provisioned/dedicated SQL pools, or Spark pools. 
 
-## Azure Private Links Hubs and Azure Virtual Network
+## Azure Private Link Hubs and Azure Virtual Network
 You must connect your Azure virtual network to the Synapse private link hub resource to secure the end-to-end connection to Synapse Studio. For this, you must create a private endpoint from your virtual network to the private link hub you created. You can use the Azure portal for your private link hub and go to the Private endpoint section. Select "+ Private endpoint" to create a new private endpoint that connects to your private link hub.
 
 :::image type="content" source="./media/synapse-private-link-hubs/synapse-private-links-private-endpoint.png" alt-text="Screenshot that shows the private endpoint connections page.":::