Add notice on GetMigrationJobProgress to AMR API overview (SharePoint#10340)

* Create migration-job-progress-api-reference.md

* Update migration-job-progress-api-reference.md

* Update migration-job-progress-api-reference.md

Revised broken links

* Update migration-job-progress-api-reference.md

Replace with relative links

* fix markdown issues, grammar, typos

## markdown

in accordance with msdocs guidelines, applied the following changes:

- always have empty lines between headings, paragraphs, and fenced code blocks
- fenced code language fixes:
  - no such language **rest**... changed to `http` or `json` where applicable
- used inline formatting where applicable

* Add notice on GetMigrationJobProgress API

* Add notice on GetMigrationJobProgress API in Migration API Reference

* update doc date

* update doc date

* Add notice of GetMigrationJobProgress to AMR API overview

* markdown formatting & grammar fixes

* markdown formatting & grammar fixes

WRT markdown, for blockquotes, new ilnes shoudl be seperated by an empty line

---------

Co-authored-by: Andrew Connell <[email protected]>

Author: shiongzuo

docs/apis/export-amr-api.md

@@ -1,7 +1,7 @@
 ---
 title: "SharePoint Asynchronous Metadata Read (AMR) API Introduction"
-description: This document is an overview on how to read metadata from SharePoint, targeted to SharePoint migration tool developers.
-ms.date: 04/18/2024
+description: Overview how to read metadata from SharePoint, targeted to SharePoint migration tool developers.
+ms.date: 07/23/2025
 ms.author: ranren
 author: underreview
 manager: dapodean
@@ -15,9 +15,9 @@ ms.collection:
 ---
 # SharePoint Asynchronous Metadata Read (AMR) API Introduction
 
-The SharePoint Asynchronous Metadata Read (AMR) API asynchronously exports metadata from SharePoint and OneDrive.
+The SharePoint Asynchronous Metadata Read (AMR) API enables the asynchronous export of metadata from SharePoint and OneDrive.
 
-Use AMR API to export metadata from SharePoint, for incremental migration, and post-migration validation.
+Use AMR API to export metadata from SharePoint for incremental migration and post-migration validation.
 
 AMR is designed exclusively for import scenarios. It exhibits poor scalability when handling requests for metadata, permissions, or versions. We can't provide performance assurances for AMR usage in data export scenarios, such as cross-tenant migrations.
 
@@ -33,6 +33,11 @@ Export metadata from SharePoint in three steps:
 
 ### Provision the destination containers and the queue
 
+> [!IMPORTANT]
+> Use [GetMigrationJobProgress API](migration-job-progress-api-reference.md) to retrieve migration job status.
+>
+> Provisioning Azure Queues for migration job status tracking is no longer required. Deprecation of Azure Queues is planned for the second half of 2026. Until then, Azure Queues will remain available for status retrieval.
+
 Use `ProvisionMigrationContainers` method to provision the containers. Check [Use Azure Blob Storage Containers and Azure Queues with Migration API](migration-azure.md) for details. You can also use your own containers and queues if needed.
 
 ### Use `CreateSPAsyncReadJob` method to start the export
@@ -47,19 +52,24 @@ Check [AMR API Reference](amr-api-reference.md) for details.
 
 ### Checking status
 
+> [!IMPORTANT]
+> Use [GetMigrationJobProgress API](migration-job-progress-api-reference.md) to retrieve migration job status.
+> 
+> Provisioning Azure Queues for migration job status tracking is no longer required. Deprecation of Azure Queues is planned for the second half of 2026. Until then, Azure Queues will remain available for status retrieval.
+
 Check Azure Queue supplied for export status. Monitor events as listed in [Events](migration-events.md) for details.
 
-AMR API exports metadata in the manifest container supplied, under folder named by `JobID`. Check [Manifest files](migration-manifest.md) for the format and validation of the metadata.
+AMR API exports metadata in the manifest container supplied, under a folder named by `JobID`. Check [Manifest files](migration-manifest.md) for the format and validation of the metadata.
 
-AMR API splits manifest package larger than 25 MB into multiple manifest files per request.
+AMR API splits manifest packages larger than 25 MB into multiple manifest files per request.
 
 ## Best practice
 
 AMR API is powerful. Ensure good performance to achieve the scale for large migration projects.
 
 ### Export security and permissions on top level if possible
 
-Exporting security with `IncludeSecurity` consumes more resources and slows down the export. It's faster to export these metadata at upper-level folder first, then export the children without them.
+Exporting security with `IncludeSecurity` consumes more resources and slows down the export. It's faster to export this metadata at the upper-level folder first, then export the children without them.
 
 ### Metadata export on a single item
 
@@ -90,9 +100,9 @@ AMR API processes jobs through a queue mechanism with preconfigured workload man
 
 ### Lab-tested performance baseline
 
-We tested the performance in lab setting. AMR API exported about 400 items per second for every 250-K objects, in the average case. The peak performance reached 700 items per second.
+We tested the performance in a lab setting. AMR API exported about 400 items per second for every 250-K objects, in the average case. The peak performance reached 700 items per second.
 
-There are multiple factors that affect the real-life performance. These factors include:
+Multiple factors affect real-life performance. These factors include:
 
 - The number of items that are being exported
 - The way AMR API is implemented
@@ -108,6 +118,6 @@ To ensure good user experiences for all Microsoft 365 customers, SharePoint uses
 
 ### Tenant-to-Tenant migrations
 
-AMR isn't intended for scenario where contents from a SharePoint tenant are moved to another. This type of migration requires the use of many resource-heavy read options. The long processing time of these read options slows down the overall migration significantly.
+AMR isn't intended for scenarios where contents from a SharePoint tenant are moved to another. This type of migration requires the use of many resource-heavy read options. The long processing time of these read options slows down the overall migration significantly.
 
 Microsoft provides no performance guarantee in this scenario. Use Graph or CSOM as needed.

docs/apis/migration-api-overview.md

@@ -1,6 +1,6 @@
 ---
 title: "SharePoint Import Migration API"
-description: "This article provides overview information on how to use the SharePoint Migration API."
+description: "This article provides an overview of how to use the SharePoint Migration API."
 ms.date: 07/16/2025
 ms.author: ranren
 author: underreview
@@ -15,7 +15,7 @@ ms.collection:
 ---
 # SharePoint Migration API Introduction
 
-The SharePoint Migration API imports contents into SharePoint at scale. It processes content and manifest packages as jobs in a queue. The API provides process status and logs, making it easy to monitor the progress of each migration job.
+The SharePoint Migration API imports content into SharePoint at scale. It processes content and manifest packages as jobs in a queue. The API provides process status and logs, making it easy to monitor the progress of each migration job.
 
 Use Migration API to migrate content from file shares, SharePoint Server, and other cloud-based services.
 
@@ -27,7 +27,7 @@ We applied quota on *Share with Me* items per user. Check [ShareWithMe event quo
 
 ### November 2024
 
-Migration API supports generating logs of all file-level events during migration to support auditing.
+We enabled logging all file-level events during migration, such as file deletion, to support auditing.
 
 ### July 2024
 
@@ -48,7 +48,8 @@ Start a migration job with three steps. Check the guidance in each of the steps
 ### Provision the destination containers and the queue
 
 > [!IMPORTANT]
-> Use [GetMigrationJobProgress API](migration-job-progress-api-reference.md) to retrieve migration job status. 
+> Use [GetMigrationJobProgress API](migration-job-progress-api-reference.md) to retrieve migration job status.
+> 
 > Provisioning Azure Queues for migration job status tracking is no longer required. Deprecation is planned for the second half of 2026. Until then, Azure Queues will remain available for status retrieval.
 
 Use the `ProvisionMigrationContainers` method to provision the containers. Check [Use Azure Blob Storage Containers and Azure Queues with Migration API](migration-azure.md) for details. You can also use your own containers and queues if needed.
@@ -86,7 +87,7 @@ Migration generates workload to the SharePoint backend differently from end user
 
 Don't use user mode in your migration solution. Running migration in user mode triggers increased throttling, resulting in poor performance.
 
-To learn more on how to register an app ID and how to implement app-based authentication, check [How to register an app ID](/azure/active-directory/develop/active-directory-v2-registration-portal) and [Microsoft Graph Auth guidance](/graph/auth).
+To learn more about how to register an app ID and how to implement app-based authentication, check [How to register an app ID](/azure/active-directory/develop/active-directory-v2-registration-portal) and [Microsoft Graph Auth guidance](/graph/auth).
 
 ### Microsoft Entra ID Permissions
 
@@ -95,17 +96,17 @@ Permissions and consent in the Azure Active Directory v1.0 endpoint](/azure/acti
 
 For SharePoint and OneDrive migration scenarios, follow the Microsoft Entra ID permission specification.
 
-For migration tools that rely on end-user signed in and presence, use Delegated permission.
+For migration tools that rely on end-user sign-in and presence, use Delegated permission.
 
 For service-based migration tools that run without a signed-in user present, such as applications that run as background services, use Application permission.
 
 ### App IDs
 
-You can choose to share a single App ID to cover multiple migration solutions created or create individual App ID for each of the products. Make sure to register App IDs. Sharing App IDs doesn't affect performance or throttling.
+You can choose to share a single App ID to cover multiple migration solutions created or create an individual App ID for each of the products. Make sure to register App IDs. Sharing App IDs doesn't affect performance or throttling.
 
 ### Keep destination SharePoint Site unactivated
 
-To avoid migration issues, deactivate the target site for users until the migration completion. The source could remain active, allowing read and write to keep productivity. Switch users to the new SharePoint destination sites after migration completion.
+To avoid migration issues, deactivate the target site for users until migration completion. The source could remain active, allowing read and write access to keep productivity. Switch users to the new SharePoint destination sites after migration completion.
 
 ## Performance