Merge branch 'SharePoint:main' into 530update

Author: cindylay

.openpublishing.redirection.json

@@ -144,11 +144,6 @@
       "source_path": "docs/embedded/terms-of-service.md",
       "redirect_url": "/sharepoint/dev/embedded/overview",
       "redirect_document_id": false
-    },
-    {
-      "source_path": "docs/embedded/tutorials/metadata.md",
-      "redirect_url": "/sharepoint/dev/embedded/overview",
-      "redirect_document_id": false
     }
   ]
 }

assets/ace/URL.txt

@@ -0,0 +1 @@
+me/events?$select=subject,body,bodyPreview,organizer,attendees,start,end,___location

docs/apis/migration-api-overview.md

@@ -1,7 +1,7 @@
 ---
 title: "SharePoint Import Migration API"
 description: "This article provides overview information on how to use the SharePoint Migration API."
-ms.date: 04/28/2024
+ms.date: 07/03/2024
 ms.author: ranren
 author: underreview
 manager: dapodean
@@ -21,6 +21,10 @@ Use Migration API to migrate content from file shares, SharePoint Server, and ot
 
 ## What's new
 
+### 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.
+
 ### 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.
@@ -61,7 +65,7 @@ Migration API generates logs in the manifest container. Check the log entries fo
 
 ### Use app-based authentication
 
-Migration generates workload to the SPO backend differently from end user-generated traffic. To properly allocate resources with our elastic capability, only use app-based authentication in your migration solution.
+Migration generates workload to the SharePoint backend differently from end user-generated traffic. To properly allocate resources with our elastic capability, only use app-based authentication in your migration solution.
 
 Don't use user mode in your migration solution. Running migration in user mode triggers increased throttling, resulting in poor performance.
 
@@ -82,28 +86,28 @@ For service-based migration tools that run without a signed-in user present, suc
 
 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.
 
-### Keep destination SPO site unactivated
+### 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 SPO destination sites after migration completion.
+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.
 
 ## Performance
 
-Migration API processes jobs through a queue mechanism with pre-configured workload management settings. Migration API processes the jobs on a best-effort basis, without Service Level Agreement (SLA) or guaranteed performance.
+Migration API processes jobs through a queue mechanism with preconfigured workload management settings. Migration API processes the jobs on a best-effort basis, without Service Level Agreement (SLA) or guaranteed performance.
 
 ### Optimize migration performance
 
 In order to ensure optimal performance for your migration projects, it's important to plan carefully, especially when dealing with large-scale migrations. For more information on how to estimate timespans and optimize performance, see our [performance guide](/sharepointmigration/sharepoint-online-and-onedrive-migration-speed).
 
 ### I'm seeing throttling messages
 
-To ensure good user experiences for all Microsoft 365 customers, SharePoint uses throttling to protect the SharePoint Online infrastructure. Avoid getting throttled by following [throttling guidance](https://aka.ms/spo429).
+To ensure good user experiences for all Microsoft 365 customers, SharePoint uses throttling to protect the SharePoint infrastructure. Avoid getting throttled by following [throttling guidance](https://aka.ms/spo429).
 
-## Special topics
+## Special articles
 
 ### Migrating sharing events of files and folders
 
 Check [Sharing events](/sharepoint/dev/apis/migration-api-shared) article for instructions when migrating shared events metadata with files and folders.
 
 ### Web Parts
 
-Use SPMT's Web Part serializer DLL to migrate Web Parts into SharePoint. Check [Migrate Web Parts](/sharepoint/dev/apis/migrate-webparts-with-migrationapi) for instructions.
+Use SharePoint Migration Tool (SPMT)'s Web Part serializer DLL to migrate Web Parts into SharePoint. Check [Migrate Web Parts](/sharepoint/dev/apis/migrate-webparts-with-migrationapi) for instructions.

docs/apis/migration-azure.md

@@ -1,7 +1,7 @@
 ---
 title: "Use Azure Blob Storage Containers and Azure Queues with SharePoint Migration API"
 description: "This article provides in-depth information on how to use the SharePoint Migration API with Azure Containers and Queues."
-ms.date: 05/08/2024
+ms.date: 07/03/2024
 ms.author: ranren
 author: underreview
 manager: dapodean
@@ -32,9 +32,9 @@ Migration API provisions the containers in the same datacenter of the SharePoint
 
 Migration API destroys Used containers 30-90 days after completing migration jobs.
 
-#### Decorate the traffic to avoid throttling
+#### Avoid throttling by decorating the traffic
 
-[Decorate your HTTP traffic](/sharepoint/dev/general-development/how-to-avoid-getting-throttled-or-blocked-in-sharepoint-online#how-to-decorate-your-http-traffic) to avoid throttling.
+Avoid throttling by [decorating your HTTP traffic](/sharepoint/dev/general-development/how-to-avoid-getting-throttled-or-blocked-in-sharepoint-online#how-to-decorate-your-http-traffic).
 
 #### Encryption
 
@@ -76,6 +76,8 @@ Pass this value to `CreateMigrationJob` method as `azureContainerSourceUri` para
 
 The SAS access token contains `Read` and `Write` permissions only. It doesn't contain `List`.
 
+SharePoint enforces HTTPS connections to containers by setting `spr=https` field in SAS tokens.
+
 ###### MetadataContainer value
 
 A **Uri** value containing the URI of the newly created container for storing **manifest** files, along with the SAS access token.
@@ -84,6 +86,8 @@ Pass this value to `CreateMigrationJob` method as `azureContainerManifestUri` pa
 
 The SAS access token contains `Read` and `Write` permissions only. It doesn't contain `List`.
 
+SharePoint enforces HTTPS connections to containers by setting `spr=https` field in SAS tokens.
+
 ###### EncryptionKey
 
 A **Byte Array** value containing the AES256CBC encryption key for both containers provisioned.
@@ -102,9 +106,9 @@ Alternatively, use user-provided Azure Queues if desired. Check the requirement
 
 ### Azure Queue Encryption
 
-When using `CreateMigrationJobEncrypted` method, Migration API encrypts the messages written to the Azure Queue.
+`CreateMigrationJobEncrypted` method encrypts the messages written to the Azure Queue.
 
-Make sure you preserve `JobId` and the `IV` values returned by `CreateMigrationJobEncrypted` method, to decrypt the message.
+To decrypt the messages, make sure you preserve `JobId` and the `IV` values returned by `CreateMigrationJobEncrypted` method.
 
 #### Encrypted message sample
 

docs/apis/webhooks/webhooks-reference-implementation.md

@@ -1,7 +1,7 @@
 ---
 title: SharePoint webhooks sample reference implementation
 description: This SharePoint Patterns and Practices (PnP) reference implementation shows how you can use SharePoint webhooks in your application.
-ms.date: 09/23/2022
+ms.date: 06/05/2024
 ms.localizationpriority: high
 ---
 # SharePoint webhooks sample reference implementation
@@ -10,19 +10,16 @@ The SharePoint Patterns and Practices (PnP) reference implementation shows how y
 
 The reference implementation only works with [SharePoint list webhooks](./lists/overview-sharepoint-list-webhooks.md).
 
-You can also follow these steps by watching the video on the Microsoft 365 Platform Communtiy (PnP) YouTube Channel:
-
-<br/>
+You can also follow these steps by watching the video on the Microsoft 365 Platform Community (PnP) YouTube Channel:
 
 > [!Video https://www.youtube.com/embed/P4a1_EWokwM]
 
-<br/>
-
 **Applies to** Office 365 Multi Tenant (MT).
 
 Microsoft Azure is used to host the various components needed to implement SharePoint webhooks.
 
 Source code and other materials for the reference implementation are available in two flavors:
+
 - A SharePoint provider-hosted application version
 - An Office 365 Azure AD application, which can be found in the [SharePoint developer samples GitHub repository](https://aka.ms/sp-webhooks-sample-reference).
 
@@ -35,9 +32,7 @@ The application shows you how to manage webhooks, specifically for a SharePoint
 ### Deployment guides
 
 - The [SharePoint webhooks reference implementation deployment guide](https://github.com/SharePoint/sp-dev-samples/blob/master/Samples/WebHooks.List/Deployment%20guide.md) lists the deployment steps used to deploy the SharePoint provider-hosted reference implementation.
-
 - To deploy the Office 365 Azure AD application, use the steps described at [SharePoint webhooks Azure AD reference implementation deployment guide](https://github.com/SharePoint/sp-dev-samples/blob/master/Samples/WebHooks.List.AzureAD/Deployment%20guide.md), which shows you how to use a Web API function as webhook service.
-
 - If you're more interested in using Azure Functions, see the [Azure Functions guide](https://github.com/SharePoint/sp-dev-samples/blob/master/Samples/WebHooks.List.AzureAD/azure%20functions%20guide.md) for more details on how to use Azure Functions in this reference implementation.
 
 ### Introduction to webhooks
@@ -48,9 +43,9 @@ Webhooks notify your application about changes in SharePoint that the applicatio
 
 The reference implementation works with a SharePoint list. To add a webhook to a SharePoint list, your application first creates a webhook subscription by sending a [`POST /_api/web/lists('list-id')/subscriptions`](./lists/create-subscription.md) request. The request includes the following items:
 
-* A payload that identifies the list that you're adding the webhook for.
-* The ___location of your webhook service URL to send the notifications.
-* The expiration date of the webhook.
+- A payload that identifies the list that you're adding the webhook for.
+- The ___location of your webhook service URL to send the notifications.
+- The expiration date of the webhook.
 
 After you've requested SharePoint to add your webhook, SharePoint validates that your webhook service endpoint exists. It sends a validation string to your service endpoint. SharePoint expects that your service endpoint returns the validation string within 5 seconds. If this process fails, the webhook creation is canceled. If you've deployed your service, this works and SharePoint returns an HTTP 201 message on the POST request that the application initially sent. The payload in the response contains the ID of the new webhook subscription.
 
@@ -74,8 +69,6 @@ public async Task<SubscriptionModel> AddListWebHookAsync(string siteUrl, string
 }
 ```
 
-<br/>
-
 When making a call to SharePoint, you need to provide authentication information, and in this case you're using a **Bearer** authentication header with an **access token**. To obtain the access token, intercept the token via an **ExecutingWebRequest** event handler:
 
 ```csharp
@@ -89,7 +82,7 @@ cc.ExecutingWebRequest += Cc_ExecutingWebRequest;
 // Capture the OAuth access token since we want to reuse that one in our REST requests
 private void Cc_ExecutingWebRequest(object sender, WebRequestEventArgs e)
 {
-    this.accessToken = e.WebRequestExecutor.RequestHeaders.Get("Authorization").Replace("Bearer ", "");
+  this.accessToken = e.WebRequestExecutor.RequestHeaders.Get("Authorization").Replace("Bearer ", "");
 }
 ```
 
@@ -123,7 +116,6 @@ To avoid getting the same change repeatedly, it's important that you inform Shar
 The following are some key things to note about changes:
 
 - SharePoint does not call your service in real-time: when a change happens on a list that has a webhook, SharePoint queues a webhook callout. Once each minute, this queue is read and the appropriate service endpoints are called. This batching of requests is important. For example, if a bulk upload of 1000 records occurred at once, batching prevents SharePoint from calling your endpoint 1000 times. So your endpoint is only called once, but when you call the `GetChanges()` method, you get 1000 change events that you need to process.
-
 - To guarantee an immediate response, regardless of the number of changes there, it's important that the workload of your service endpoint runs asynchronously. In the reference implementation, we leveraged the power of Azure: the service serializes the incoming payload and stores it in an Azure Storage queue while there's an Azure web job that runs continuously and checks for messages in the queue. When there are messages in the queue, the web job processes them and also executes your logic asynchronously.
 
 ## Complete end-to-end flow
@@ -157,7 +149,7 @@ Create a web job that on a weekly basis reads all the subscription IDs from the
 > [!NOTE]
 > This web job is not part of this reference implementation.
 
-The actual renewal of a SharePoint list webhook can be done by using a `[PATCH /_api/web/lists('list-id')/subscriptions(‘subscriptionID’)](./lists/update-subscription.md)` REST call.
+The actual renewal of a SharePoint list webhook can be done by using a [`PATCH /_api/web/lists('list-id')/subscriptions(‘subscriptionID’)`](./lists/update-subscription.md) REST call.
 
 In the reference implementation, updating of webhooks is implemented in the [WebHookManager](https://github.com/SharePoint/sp-dev-samples/blob/master/Samples/WebHooks.List/SharePoint.WebHooks.Common/WebHookManager.cs) class of the **SharePoint.WebHooks.Common** project.
 
@@ -176,18 +168,16 @@ Updating a webhook is done by using the **UpdateListWebHookAsync** method:
 /// <returns>true if successful, exception in case something went wrong</returns>
 public async Task<bool> UpdateListWebHookAsync(string siteUrl, string listId, string subscriptionId, string webHookEndPoint, DateTime expirationDateTime, string accessToken)
 {
-    // webhook update code...
+  // webhook update code...
 }
 ```
 
 ## Debugging webhooks
 
 Because SharePoint is calling out to your webhook service endpoint, your endpoint needs to be reachable by SharePoint. This makes development and debugging slightly more complex. The following are some strategies that you can use to make your life easier:
 
-* During initial development, you provide your own serialized payload to your service processing logic. This makes it possible to completely test your processing logic without deploying the service endpoint (and even without configuring a webhook).
-
-* If you have access to Azure resources, you can deploy your endpoint to Azure by using a debug build and configuring the Azure App Service for debugging. This allows you to set a remote breakpoint and do remote debugging using Visual Studio.
-
+- During initial development, you provide your own serialized payload to your service processing logic. This makes it possible to completely test your processing logic without deploying the service endpoint (and even without configuring a webhook).
+- If you have access to Azure resources, you can deploy your endpoint to Azure by using a debug build and configuring the Azure App Service for debugging. This allows you to set a remote breakpoint and do remote debugging using Visual Studio.
 - If you do not want to deploy your service during development time, you need to use a secure tunnel for your service. The idea is that you tell SharePoint that the notification service is located on a shared public endpoint. In the client, you install a component that connects to that shared public service, and whenever a call is made to the public endpoint, the client component is notified and it pushes the payload to your service running on localhost. [ngrok](https://ngrok.com/) is an implementation of such a secure tunnel tool that you can use to debug your webhook service locally.
 
 ## See also

docs/declarative-customization/site-design-o365cli.md

@@ -1,7 +1,7 @@
 ---
 title: SharePoint site design - CLI for Microsoft 365 commands
 description: Use the CLI for Microsoft 365 to create, retrieve, and remove site designs and site scripts.
-ms.date: 06/28/2022
+ms.date: 06/27/2024
 ms.localizationpriority: high
 ---
 
@@ -17,7 +17,7 @@ To run the CLI for Microsoft 365 commands, you'll need to do the following:
 
 1. Download and install [NodeJS LTS version](https://nodejs.org/en/)
 1. Follow the instructions at [Installing the CLI](https://pnp.github.io/cli-microsoft365/user-guide/installing-cli/) to install the CLI for Microsoft 365 on your machine
-1. Follow the instructions at [Logging in to Office 365](https://pnp.github.io/cli-microsoft365/user-guide/connecting-office-365/) to connect to your SharePoint tenant.
+1. Follow the instructions at [Logging in to Office 365](https://pnp.github.io/cli-microsoft365/user-guide/connecting-microsoft-365) to connect to your SharePoint tenant.
 
 To verify your setup and connection, try using the [sitedesign list](https://pnp.github.io/cli-microsoft365/cmd/spo/sitedesign/sitedesign-list) command to read the current list of site designs. If the cmdlet runs and returns with no errors, you're ready to proceed.
 

docs/declarative-customization/site-design-trigger-flow-tutorial.md

@@ -1,7 +1,7 @@
 ---
 title: Using site designs and Power Automate to track site creation requests
 description: Invoke a Power Automate flow using the site script triggerFlow action to capture the site creation event and build a site directory. This tutorial is intended to illustrate a simple example of using site designs and Power Automate.
-ms.date: 06/28/2022
+ms.date: 06/05/2024
 ms.localizationpriority: high
 ---
 
@@ -68,7 +68,7 @@ In order to capture the site creation event and create the corresponding list it
             "type": "string"
           },
           "creatorEmail": {
-            "type": "string"
+            "type": ["string", "null"]
           },
           "createdTimeUTC": {
             "type": "string"

docs/embedded/concepts/admin-exp/adminrole.md

@@ -9,7 +9,7 @@ ms.localizationpriority: high
 
 The SharePoint Embedded administrator is a dedicated role to manage SharePoint Embedded containers through [SharePoint PowerShell](/powershell/module/sharepoint-online/connect-sposervice) and SharePoint admin center. This role is required for [developer admins](./developer-admin/dev-admin.md) to create new container types through PowerShell cmdlets and also for consuming tenant admins to manage containers created in their tenants.
 
-The global administrator role already has all the permissions of the SharePoint Embedded administrator role. A SharePoint administrator can assign themselves the SharePoint Embedded administrator role to act as a consuming tenant admin or a developer administrator for SharePoint Embedded.
+The global administrator role already has all the permissions of the SharePoint Embedded administrator role. A global administrator can assign a user the SharePoint Embedded administrator role to act as a consuming tenant admin or a developer administrator for SharePoint Embedded.
 
 The SharePoint Embedded administrator role is available in Microsoft Entra and Microsoft 365 Admin Center. This role doesn't have access to site management. This means that a SharePoint Embedded administrator can't see 'Active sites' and 'Deleted sites' pages on the SharePoint Admin Center and also can't run site specific PowerShell cmdlets.