Merge branch 'readonly' of https://github.com/cindylay/sp-dev-docs-cindy into readonly

Author: cindylay

.openpublishing.redirection.json

@@ -177,97 +177,97 @@
     },
     {
       "source_path": "docs/embedded/concepts/admin-exp/consuming-tenant-admin/ctapowershell.md ",
-      "redirect_url": "sharepoint/dev/embedded/administration/consuming-tenant-admin/ctapowershell",
+      "redirect_url": "/sharepoint/dev/embedded/administration/consuming-tenant-admin/ctapowershell",
       "redirect_document_id": false
     },
     {
       "source_path": "docs/embedded/concepts/admin-exp/developer-admin/dev-admin.md",
-      "redirect_url": "sharepoint/dev/embedded/administration/developer-admin/dev-admin",
+      "redirect_url": "/sharepoint/dev/embedded/administration/developer-admin/dev-admin",
       "redirect_document_id": false
     },
     {
       "source_path": "docs/embedded/concepts/security-and-compliance.md",
-      "redirect_url": "sharepoint/dev/embedded/compliance/security-and-compliance",
+      "redirect_url": "/sharepoint/dev/embedded/compliance/security-and-compliance",
       "redirect_document_id": false
     },
     {
       "source_path": "docs/embedded/concepts/app-concepts/app-architecture.md",
-      "redirect_url": "sharepoint/dev/embedded/development/app-architecture",
+      "redirect_url": "/sharepoint/dev/embedded/development/app-architecture",
       "redirect_document_id": false
     },
     {
       "source_path": "docs/embedded/concepts/app-concepts/auth.md",
-      "redirect_url": "sharepoint/dev/embedded/development/auth",
+      "redirect_url": "/sharepoint/dev/embedded/development/auth",
       "redirect_document_id": false
     },
     {
       "source_path": "docs/embedded/concepts/content-experiences/office-experience.md",
-      "redirect_url": "sharepoint/dev/embedded/development/content-experiences/office-experience",
+      "redirect_url": "/sharepoint/dev/embedded/development/content-experiences/office-experience",
       "redirect_document_id": false
     },
     {
       "source_path": "docs/embedded/concepts/content-experiences/search-content.md",
-      "redirect_url": "sharepoint/dev/embedded/development/content-experiences/search-content",
+      "redirect_url": "/sharepoint/dev/embedded/development/content-experiences/search-content",
       "redirect_document_id": false
     },
     {
       "source_path": "docs/embedded/concepts/content-experiences/user-experiences-overview.md",
-      "redirect_url": "sharepoint/dev/embedded/development/content-experiences/user-experiences-overview",
+      "redirect_url": "/sharepoint/dev/embedded/development/content-experiences/user-experiences-overview",
       "redirect_document_id": false
     },
     {
       "source_path": "docs/embedded/concepts/fluid.md",
-      "redirect_url": "sharepoint/dev/embedded/development/fluid",
+      "redirect_url": "/sharepoint/dev/embedded/development/fluid",
       "redirect_document_id": false
     },
     {
       "source_path": "docs/embedded/concepts/app-concepts/limits-calling.md",
-      "redirect_url": "sharepoint/dev/embedded/development/limits-calling",
+      "redirect_url": "/sharepoint/dev/embedded/development/limits-calling",
       "redirect_document_id": false
     },
     {
       "source_path": "docs/embedded/concepts/app-concepts/sharing-and-perm.md",
-      "redirect_url": "sharepoint/dev/embedded/development/sharing-and-perm",
+      "redirect_url": "/sharepoint/dev/embedded/development/sharing-and-perm",
       "redirect_document_id": false
     },
     {
       "source_path": "docs/embedded/tutorials/doc-processing-acs.md",
-      "redirect_url": "sharepoint/dev/embedded/development/tutorials/doc-processing-acs",
+      "redirect_url": "/sharepoint/dev/embedded/development/tutorials/doc-processing-acs",
       "redirect_document_id": false
     },
     {
       "source_path": "docs/embedded/tutorials/launch-experience.md",
-      "redirect_url": "sharepoint/dev/embedded/development/tutorials/launch-experience",
+      "redirect_url": "/sharepoint/dev/embedded/development/tutorials/launch-experience",
       "redirect_document_id": false
     },
     {
       "source_path": "docs/embedded/tutorials/metadata.md",
-      "redirect_url": "sharepoint/dev/embedded/development/tutorials/metadata",
+      "redirect_url": "/sharepoint/dev/embedded/development/tutorials/metadata",
       "redirect_document_id": false
     },
     {
       "source_path": "docs/embedded/tutorials/migrate-abs-to-spe.md",
-      "redirect_url": "sharepoint/dev/embedded/development/tutorials/migrate-abs-to-spe",
+      "redirect_url": "/sharepoint/dev/embedded/development/tutorials/migrate-abs-to-spe",
       "redirect_document_id": false
     },
     {
       "source_path": "docs/embedded/tutorials/using-file-preview.md",
-      "redirect_url": "sharepoint/dev/embedded/development/tutorials/using-file-preview",
+      "redirect_url": "/sharepoint/dev/embedded/development/tutorials/using-file-preview",
       "redirect_document_id": false
     },
     {
       "source_path": "docs/embedded/tutorials/using-webhooks.md",
-      "redirect_url": "sharepoint/dev/embedded/development/tutorials/using-webhooks",
+      "redirect_url": "/sharepoint/dev/embedded/development/tutorials/using-webhooks",
       "redirect_document_id": false
     },
     {
       "source_path": "docs/embedded/concepts/app-concepts/containertypes.md",
-      "redirect_url": "sharepoint/dev/embedded/getting-started/containertypes",
+      "redirect_url": "/sharepoint/dev/embedded/getting-started/containertypes",
       "redirect_document_id": false
     },
     {
       "source_path": "docs/embedded/concepts/app-concepts/register-api-documentation.md",
-      "redirect_url": "sharepoint/dev/embedded/getting-started/register-api-documentation",
+      "redirect_url": "/sharepoint/dev/embedded/getting-started/register-api-documentation",
       "redirect_document_id": false
     }
   ]

docs/apis/migration-api-overview.md

@@ -21,13 +21,21 @@ Use Migration API to migrate content from file shares, SharePoint Server, and ot
 
 ## What's new
 
+### December 2024
+
+We applied quota on *Share with Me* items per user. Check [ShareWithMe event quota](/sharepoint/dev/apis/migration-api-shared#quota) for more detail.
+
+### November 2024
+
+Migration API supports generating logs of all file-level events during migration to support auditing.
+
 ### July 2024
 
-We started enforcing HTTPS connection to SharePoint provided Azure Blob Storage Containers by adding a `spr=https` field in SAS tokens. This enforcement is fully effective on July 21, 2024. Check [Use Azure Blob Storage Containers and Azure Queues with SharePoint Migration API](migration-azure.md) for details.
+We started enforcing HTTPS connections to SharePoint-provided Azure Blob Storage Containers by adding a `spr=https` field in SAS tokens. This enforcement will be fully effective on July 21, 2024. Check [Use Azure Blob Storage Containers and Azure Queues with SharePoint Migration API](migration-azure.md) for details.
 
 ### April 2024
 
-We added new fields in ``JobEnd`` events to indicate the count and bytes imported for files. Check [Migration events in Azure Queue](migration-events.md#jobend-import) for details.
+We added new fields in `JobEnd` events to indicate the count and bytes imported for files. Check [Migration events in Azure Queue](migration-events.md#jobend-import) for details.
 
 ### January 2024
 
@@ -39,7 +47,7 @@ Start a migration job with three steps. Check the guidance in each of the steps
 
 ### Provision the destination containers and the queue
 
-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 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.
 
 ### Prepare the content
 
@@ -55,12 +63,14 @@ Check [Manifest files](migration-manifest.md) to see the detailed requirements.
 
 ### Use Migration API to start the migration and get status
 
-`CreateMigrationJob` method creates a migration job, which is queued up for processing. Migration API manages the queue and returns status and logs. Use `CreateMigrationEncrypted` method to migrate encrypted contents. Check [SharePoint Migration API Reference](migration-api-reference.md) for details.
+The `CreateMigrationJob` method creates a migration job, which is queued up for processing. Migration API manages the queue and returns status and logs. Use the `CreateMigrationEncrypted` method to migrate encrypted contents. Check [SharePoint Migration API Reference](migration-api-reference.md) for details.
 
-Upon creation of a new migration job, Migration API returns the Job ID. Track the status of the import with `GetMigrationJobStatus` method if needed, with the Azure Queue supplied.
+Upon creation of a new migration job, Migration API returns the Job ID. Track the status of the import with the `GetMigrationJobStatus` method if needed, with the Azure Queue supplied.
 
 Migration API generates logs in the manifest container. Check the log entries for migration results.
 
+Migration API also generates logs of file-level activities performed by migration. The supported file-level activities include FileUploaded, FileDeleted, FileRenamed, FileMoved. Check M365 Admin Center for activity details when needed.
+
 ## Best Practice
 
 ### Use app-based authentication

docs/apis/migration-api-shared.md

@@ -2,9 +2,9 @@
 title: "SPO Migration API: Migrating shared files and folders"
 description: "Migrating shared files and folders using item references."
 ms.date: 06/28/2022
-ms.author: jhendr
-author: JoanneHendrickson
-manager: pamgreen
+ms.author: jihongzuo
+author: shiongzuo
+manager: Dan.Podeanu
 ms.topic: article
 ms.subservice: migration-tool
 ---
@@ -34,34 +34,41 @@ Add a SharedWithMember block for each person that the item was shared with durin
     </SharedWithEvent>
   </SharedWithEvents>
 </ListItem>
-
 ```
+
 ## Best Practices
+
 ### The basics
+
 For each file or folder that was shared with a user in the source, create an item reference for that item in the recipient’s OneDrive. Every item reference created will appear in the user’s *Shared with Me* view in OneDrive. Remember to give the user permission to access the item as well.
 
 ### Inheritance
+
 Be sure to use inheritance correctly for sharing. When creating an item reference for a file or folder, check if its parent folder (or higher) already has an item reference created for it. If so, do not create another one for the child item. This will prevent users from seeing duplicate items in their *Shared with Me* view and reduce migration and service load as well.
 
-**Example:** When a folder is shared and the recipient can access all of the folder’s contents, an item reference should *only* be created for the shared folder -- not for its contents. The only item that should appear in the recipients *Shared with Me* is the shared folder.
+**Example:** When a folder is shared and the recipient can access all of the folder’s contents, an item reference should *only* be created for the shared folder -- not for its contents. The only item that should appear in the recipient's *Shared with Me* is the shared folder.
 
-This same guidance should also be used for permissions (ACLs). Only apply permissions on a child item where the required permissions are different than its parent item. Make sure not to exceed 5000 unique ACLs on a site.  It may be useful to check how many ACLs you create and warn the user prior to migration. There is also a hard limit of 50,000 unique ACL's that will be enforced. If you are close to reaching the 5000 limits, we recommend that the permission model be simplified on the source before migration.
+This same guidance should also be used for permissions (*access control lists, also known as ACLs*). Only apply permissions on a child item where the required permissions are different than its parent item. Make sure not to exceed 5000 unique ACLs on a site.  It may be useful to check how many ACLs you create and warn the user prior to migration. There is also a hard limit of 50,000 unique ACLs that will be enforced. If you are close to reaching the 5000 limits, we recommend that the permission model be simplified on the source before migration.
 
 ### Sharing with groups
+
 For items shared with a group of individuals in the source, the content may be migrated into a shared library (eg. a team site) in which all of those individuals are given access.
 
 ### Anonymous sharing links
+
 Do not migrate anonymous sharing links from the source; this is not useful as it’s not possible to know which users used that link in the source. Users should evaluate whether anonymous links are still needed and create new ones on the destination if so.
 
 ### Sharing with external users
+
 Before starting migration, you must ensure all users are provisioned in the customer tenant. For users external to the tenant (ie. from a different organization), provision them as B2B collaboration users in Azure Active Directory. This is done in the Azure portal following these steps:
 
 - [Add Azure Active Directory B2B collaboration users in the Azure portal](/azure/active-directory/b2b/add-users-administrator).
 
 Once the external users are provisioned, share files and folders with them during migration the same way as internal users.
 
 ### Permission and Sharing
-The per user sharing model in SharePoint relies on both permissions and “Shared With” data references for an object to be considered shared with an individual. If a user has access to content, but no “Shared With” references, they will not see the content show up in their Shared With Me view within their OneDrive For Business site.
+
+The per-user sharing model in SharePoint relies on both permissions and “Shared With” data references for an object to be considered shared with an individual. If a user has access to content, but no “Shared With” references, they will not see the content show up in their Shared With Me view within their OneDrive For Business site.
 
 However, if they are indicated in “Shared With” references but do not have any access to the content, they will either never see the content show up in their Shared With Me view within their OneDrive For Business site or when they try to use a link from there it will be denied access. To preserve sharing information, both the permissions and “Shared With” references will need to be correctly set. The permissions can be set at different levels of the content hierarchy using scopes (unique ACLs), that apply to that object and any of its children unless they themselves have unique permissions.
 
@@ -71,3 +78,7 @@ Permissions migration is performed using the DeploymentRoleAssignments object wi
 
 > [!NOTE]
 > The **Migration API** is not available for users of Office 365 operated by 21Vianet in China.
+
+### Quota
+
+Do not migrate more than 1,000 *Share with Me* events for any receiver within 24 hours. If a receiver already has 1,000 *Share with Me* events being imported within 24 hours, they will NOT receive any additional *Share with Me* events during the time window. And Import API will send back warning messages indicating some *Share with Me* events have been throttled.

docs/apis/webhooks/sharepoint-webhooks-using-azd-template.md

@@ -1,7 +1,8 @@
 ---
 title: Create Azure Functions for SharePoint webhooks using an azd template
-description: Use Azure Developer cli (azd) to deploy an Azure function app that connects to your SharePoint Online tenant, to register and manage webhooks, and process the notifications from SharePoint.
-ms.date: 02/27/2025
+description: Use Azure Developer cli (azd) to deploy an Azure function app that connects to your SharePoint Online 
+  tenant, to register and manage webhooks, and process the notifications from SharePoint.
+ms.date: 03/11/2025
 ms.localizationpriority: low
 ---
 # Azure Functions for SharePoint webhooks using azd
@@ -56,7 +57,8 @@ This tutorial assumes the system-assigned managed identity is used.
 
 Navigate to your function app in the [Azure portal](https://portal.azure.com/#blade/HubsExtension/BrowseResourceBlade/resourceType/Microsoft.Web%2Fsites/kind/functionapp) > select **Identity** and note the **Object (principal) ID** of the system-assigned managed identity.  
 
-In this tutorial, it is **d3e8dc41-94f2-4b0f-82ff-ed03c363f0f8**.  
+> [!NOTE]
+> In this tutorial, it is **d3e8dc41-94f2-4b0f-82ff-ed03c363f0f8**.  
 
 Then, use one of the scripts below to grant this identity the app-only permission **Sites.Selected** on the SharePoint API: