Merge pull request #299103 from MicrosoftDocs/repo_sync_working_branch

Taojunshen · web-flow · commit 237052e3ed78 · 2025-05-01T00:34:38.000+08:00
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
diff --git a/articles/backup/scripts/geo-code-list.md b/articles/backup/scripts/geo-code-list.md
@@ -68,7 +68,7 @@ This sample XML provides you with an insight about the geo-codes mapped with the
 <GeoCodeRegionNameMap	GeoCode="JIW"	RegionName="Jio India West"	/>
 <GeoCodeRegionNameMap	GeoCode="QAC"	RegionName="Qatar Central"	/>
 <GeoCodeRegionNameMap	GeoCode="PLC"	RegionName="Poland Central"	/>
-<GeoCodeRegionNameMap	GeoCode="MYS"	RegionName="Malaysia South"	/
+<GeoCodeRegionNameMap	GeoCode="MYS"	RegionName="Malaysia South"	/>
 <GeoCodeRegionNameMap	GeoCode="TWN"	RegionName="Taiwan North"	/>
 <GeoCodeRegionNameMap	GeoCode="TWNR"	RegionName="Taiwan Northwest"	/>
 <GeoCodeRegionNameMap	GeoCode="ILC"	RegionName="Israel Central"	/>
diff --git a/articles/communication-services/samples/trusted-auth-sample.md b/articles/communication-services/samples/trusted-auth-sample.md
@@ -44,7 +44,7 @@ To be able to run this sample, you need:
 - Update the Server (Web API) application with information from the app registrations.
  
 ::: zone pivot="programming-language-javascript"
-[!INCLUDE [NodeJS Auth Hero](./includes/node-auth-hero.md)]
+[!INCLUDE [Node.js Auth Hero](./includes/node-auth-hero.md)]
 ::: zone-end
 
 ::: zone pivot="programming-language-csharp"
diff --git a/articles/event-grid/subscribe-to-graph-api-events.md b/articles/event-grid/subscribe-to-graph-api-events.md
@@ -213,7 +213,7 @@ Web application samples are available for the following languages:
 
 - [C# sample](https://github.com/microsoftgraph/msgraph-sample-eventgrid-notifications-dotnet). It's an up-to-date sample that includes how to create and renew Graph API subscriptions and walks you through some of the steps to enable the flow of events.
 - [Java sample](https://github.com/microsoftgraph/java-spring-webhooks-sample)
-- [NodeJS sample](https://github.com/microsoftgraph/nodejs-webhooks-sample).
+- [Node.js sample](https://github.com/microsoftgraph/nodejs-webhooks-sample).
 
 > [!IMPORTANT]
 > You need to activate your partner topic that is created as part of your Graph API subscription creation. You also need to create an Event Grid event subscription to your web application to receive events. To that end, you use the URL configured in your web application to receive events as a webhook endpoint in your event subscription. [Next steps](#next-steps) for more information.
diff --git a/articles/event-hubs/schema-registry-concepts.md b/articles/event-hubs/schema-registry-concepts.md
@@ -107,7 +107,7 @@ You can use one of the following libraries to include an Avro serializer. You ca
 | **.NET** | [Microsoft.Azure.Data.SchemaRegistry.ApacheAvro](https://github.com/Azure/azure-sdk-for-net/tree/master/sdk/schemaregistry/Microsoft.Azure.Data.SchemaRegistry.ApacheAvro) | [.NET Samples](https://github.com/Azure/azure-sdk-for-net/tree/master/sdk/schemaregistry/Microsoft.Azure.Data.SchemaRegistry.ApacheAvro/tests/Samples) |
 | **Java** | [azure-data-schemaregistry-avro](https://github.com/Azure/azure-sdk-for-java/tree/main/sdk/schemaregistry/azure-data-schemaregistry-apacheavro) | [Java samples](https://github.com/Azure/azure-sdk-for-java/tree/main/sdk/schemaregistry/azure-data-schemaregistry-apacheavro/src/samples)|
 |**Python** | [azure-schemaregistry-avroserializer](https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/schemaregistry/azure-schemaregistry-avroencoder/) | [Python samples](https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/schemaregistry/azure-schemaregistry-avroencoder/samples)|
-|**JavaScript** | [@azure/schema-registry-avro](https://github.com/Azure/azure-sdk-for-js/tree/master/sdk/schemaregistry/schema-registry-avro) | [NodeJS samples](https://github.com/Azure/azure-sdk-for-js/tree/master/sdk/schemaregistry/schema-registry-avro/samples) |
+|**JavaScript** | [@azure/schema-registry-avro](https://github.com/Azure/azure-sdk-for-js/tree/master/sdk/schemaregistry/schema-registry-avro) | [Node.js samples](https://github.com/Azure/azure-sdk-for-js/tree/master/sdk/schemaregistry/schema-registry-avro/samples) |
 
 Additionally, the below libraries are also available based on your workloads.
 * **Apache Kafka**: Run [Kafka-integrated Avro](https://github.com/Azure/azure-schema-registry-for-kafka/) serializers and deserializers backed by Schema Registry. The Java client's Apache Kafka client serializer for Schema Registry can be used in any Apache Kafka scenario and with any Apache Kafka-based deployment or cloud service.
diff --git a/articles/spring-apps/basic-standard/concept-app-customer-responsibilities.md b/articles/spring-apps/basic-standard/concept-app-customer-responsibilities.md
@@ -58,7 +58,7 @@ When you deploy your polyglot applications to the Enterprise plan, assign specif
 | .NET   | [.NET and .NET core support policy](https://dotnet.microsoft.com/platform/support/policy/dotnet-core) |
 | Python | [Status of Python versions](https://devguide.python.org/versions/)                                    |
 | Go     | [Go release history](https://go.dev/doc/devel/release)                                                |
-| Node.js | [Nodejs releases](https://nodejs.org/en/about/previous-releases/)                                     |
+| Node.js | [Node.js releases](https://nodejs.org/en/about/previous-releases/)                                     |
 | PHP    | [PHP supported versions](https://www.php.net/supported-versions.php)                                  |
 
 ### Stack image support
diff --git a/articles/storage/files/storage-files-migration-overview.md b/articles/storage/files/storage-files-migration-overview.md
@@ -66,7 +66,6 @@ The following table lists supported metadata for Azure Files.
 | **Source** | **Target** |
 |------------|------------|
 | Directory structure | The original directory structure of the source can be preserved on the target share. |
-| Symbolic links | Symbolic links on the source can be preserved and mapped on the target share. |
 | Access permissions | Azure Files supports Windows ACLs, and they must be set on the target share even if no AD integration is configured at migration time. The following ACLs must be preserved: owner security identifier (SID), group SID, discretionary access lists (DACLs), system access control lists (SACLs). |
 | Create timestamp | The original create timestamp of the source file can be preserved on the target share. |
 | Change timestamp | The original change timestamp of the source file can be preserved on the target share. |
@@ -83,7 +82,7 @@ How to use the table:
 
 1. Choose one of these targets:
 
-   - **Hybrid deployment:** Use Azure File Sync to cache the content of Azure file shares on-premises and tier less frequently used files to the cloud.
+   - **Hybrid deployment:** Use [Azure File Sync](../file-sync/file-sync-introduction.md) to cache the content of Azure file shares on-premises and tier less frequently used files to the cloud.
    - **Cloud-only deployment:** Azure file shares in the cloud, with no on-premises caching.
 
    Select the target column that matches your choice.
@@ -95,10 +94,10 @@ A scenario without a link doesn't yet have a published migration guide. Check th
 | Source | Target: </br>Hybrid deployment </br>(Azure Files + Azure File Sync) | Target: </br>Cloud-only deployment </br>(Azure Files)|
 |:---|:--|:--|
 | | Recommended tool combination:| Recommended tool combination: |
-| Windows Server 2012 R2 and later | <ul><li>[Azure File Sync](../file-sync/file-sync-deployment-guide.md)</li><li>[Azure File Sync and Azure DataBox](storage-files-migration-server-hybrid-databox.md)</li></ul> | <ul><li>Via [Azure Storage Mover](migrate-files-storage-mover.md)</li><li>[Via RoboCopy to a mounted Azure file share](storage-files-migration-robocopy.md)</li><li>Via Azure File Sync: Follow same steps as [Azure File Sync hybrid deployment](../file-sync/file-sync-deployment-guide.md) and [decommission server endpoint](../file-sync/file-sync-server-endpoint-delete.md) at the end.</li></ul> |
-| Windows Server 2012 and earlier | <ul><li>Via DataBox and Azure File Sync to recent server OS</li><li>Via Storage Migration Service to recent server with Azure File Sync, then upload</li></ul> | <ul><li>Via [Azure Storage Mover](migrate-files-storage-mover.md)</li><li>Via Storage Migration Service to recent server with Azure File Sync</li><li>[Via RoboCopy to a mounted Azure file share](storage-files-migration-robocopy.md)</li></ul> |
-| Network-attached storage (NAS) | <ul><li>Via Storage Mover upload + Azure File Sync</li><li>[Via Azure File Sync upload](storage-files-migration-nas-hybrid.md)</li><li>[Via DataBox + Azure File Sync](storage-files-migration-nas-hybrid-databox.md)</li></ul> | <ul><li>Via [Azure Storage Mover](migrate-files-storage-mover.md)</li><li>[Via DataBox](storage-files-migration-nas-cloud-databox.md)</li><li>[Via RoboCopy to a mounted Azure file share](storage-files-migration-robocopy.md)</li></ul> |
-| Linux (SMB) | <ul><li>N/A</li></ul> | <ul><li>Via [Azure Storage Mover](migrate-files-storage-mover.md)</li></ul> |
+| Windows Server 2012 R2 and later | <ul><li>[Azure File Sync](../file-sync/file-sync-deployment-guide.md)</li><li>[Azure File Sync and Azure DataBox](storage-files-migration-server-hybrid-databox.md)</li></ul> | <ul><li>Via Azure File Sync: Follow same steps as [Azure File Sync hybrid deployment](../file-sync/file-sync-deployment-guide.md) and [decommission server endpoint](../file-sync/file-sync-server-endpoint-delete.md) at the end.</li><li>[Via RoboCopy to a mounted Azure file share](storage-files-migration-robocopy.md)</li><li>Via [Azure Storage Mover](migrate-files-storage-mover.md)</li></ul> |
+| Windows Server 2012 and earlier | <ul><li>Via [DataBox](../../databox/data-box-overview.md)</li><li>Via [Storage Migration Service](https://github.com/MicrosoftDocs/windowsserverdocs/blob/main/WindowsServerDocs/storage/storage-migration-service/overview.md) to recent server with [Azure File Sync](../file-sync/file-sync-deployment-guide.md), then upload</li></ul> | <ul><li>Via [Azure Storage Mover](migrate-files-storage-mover.md)</li><li>Via [Storage Migration Service](https://github.com/MicrosoftDocs/windowsserverdocs/blob/main/WindowsServerDocs/storage/storage-migration-service/overview.md) to recent server with [Azure File Sync](../file-sync/file-sync-deployment-guide.md)</li><li>[Via RoboCopy to a mounted Azure file share](storage-files-migration-robocopy.md)</li></ul> |
+| Linux (SMB) | <ul><li>NA</li></ul> | <ul><li>Via [Azure Storage Mover](migrate-files-storage-mover.md)</li></ul> |
+| Network-attached storage (NAS) | <ul><li>Via [Storage Mover upload](migrate-files-storage-mover.md) + [Azure File Sync](../file-sync/file-sync-deployment-guide.md)</li><li>[Via Azure File Sync upload](storage-files-migration-nas-hybrid.md)</li><li>[Via DataBox + Azure File Sync](storage-files-migration-nas-hybrid-databox.md)</li></ul> | <ul><li>Via [Azure Storage Mover](migrate-files-storage-mover.md)</li><li>[Via DataBox](storage-files-migration-nas-cloud-databox.md)</li><li>[Via RoboCopy to a mounted Azure file share](storage-files-migration-robocopy.md)</li></ul> |
 
 ## Migration toolbox
 
