Merge branch 'SharePoint:main' into main

Author: Fedes365

.github/CONTRIBUTING.md

@@ -108,14 +108,14 @@ remove: Total 10 (delta 1), reused 10 (delta 1)
 Unpacking objects: 100% (10/10), done.
 ```
 
-## Switch to `master` branch
+## Switch to `main` branch
 
-In order to add your changes, you will need to do those in the `master` branch.
+In order to add your changes, you will need to do those in the `main` branch.
 
-Type the following command in the console to switch to `master` branch:
+Type the following command in the console to switch to `main` branch:
 
 ```
-git checkout master
+git checkout main
 ```
 
 Now, you can update existing docs or add new docs to the docs repo.
@@ -131,15 +131,15 @@ Depending on the doc's intent, you can choose to add your doc into  `basics` or
 
 ## Submit a pull request
 
-Once you have completed adding your changes, you can submit a pull request. 
+Once you have completed adding your changes, you can submit a pull request.
 
-Navigate to the forked sp-dev-docs repo in your account. Make sure your current branch is `master` branch.
+Navigate to the forked sp-dev-docs repo in your account. Make sure your current branch is `main` branch.
 
-Once you are in the `master` branch, you should see a message stating `This branch is 1 commit ahead of SharePoint:master` and next to it will be a `Pull request` link.
+Once you are in the `main` branch, you should see a message stating `This branch is 1 commit ahead of Sharepoint:main` and next to it will be a `Pull request` link.
 
 ![Submit a pull request to sp-dev-docs repo](../images/contribute-docs-submit-pr.png)
 
-Click the `Pull request` link to start a new pull request. Make sure you use this [template](PULL_REQUEST_TEMPLATE.md) to fill in your changes. Make sure you are creating this pull request against the `master` branch.
+Click the `Pull request` link to start a new pull request. Make sure you use this [template](PULL_REQUEST_TEMPLATE.md) to fill in your changes. Make sure you are creating this pull request against the `main` branch.
 
 Once you have all the information, click the `Create pull request` button to submit your pull request.
 

README.md

@@ -4,7 +4,7 @@ The SharePoint Framework (SPFx) is a page and part model that enables client-sid
 
 * [Official SharePoint Framework Documentation](https://aka.ms/spfx)
 
-This repository contains the raw documents published to docs.microsoft.com site.
+This repository contains the raw documents published to Microsoft Docs.
 
 ## Questions & Help
 
@@ -14,20 +14,20 @@ You can also tweet / follow [@Microsoft365Dev](https://twitter.com/Microsoft365D
 
 ## SharePoint Framework Releases
 
-Review all the SPFx releases here from the initial GA release in February 2017 in the docs: https://docs.microsoft.com/sharepoint/dev/spfx/roadmap
+Review all the SPFx releases here from the [initial GA release in February 2017](https://learn.microsoft.com/sharepoint/dev/spfx/roadmap)
 
 ## Get Started
 
-* [Setup your Office 365 Developer Tenant](https://docs.microsoft.com/sharepoint/dev/spfx/set-up-your-developer-tenant)
-* [Setup your Machine](https://docs.microsoft.com/sharepoint/dev/spfx/set-up-your-development-environment)
-* [Go build your first web part](https://docs.microsoft.com/sharepoint/dev/spfx/web-parts/get-started/build-a-hello-world-web-part)
+* [Setup your Office 365 Developer Tenant](https://learn.microsoft.com/sharepoint/dev/spfx/set-up-your-developer-tenant)
+* [Setup your Machine](https://learn.microsoft.com/sharepoint/dev/spfx/set-up-your-development-environment)
+* [Go build your first web part](https://learn.microsoft.com/sharepoint/dev/spfx/web-parts/get-started/build-a-hello-world-web-part)
 
 
 ## Learn More
 
-* [Background and Philosophy](https://docs.microsoft.com/sharepoint/dev/spfx/sharepoint-framework-overview)
-* [Design Great Web Parts](https://docs.microsoft.com/sharepoint/dev/design/design-guidance-overview)
-* [API Docs](/javascript/api/sp-application-base)
+* [Background and Philosophy](https://learn.microsoft.com/sharepoint/dev/spfx/sharepoint-framework-overview)
+* [Design Great Web Parts](https://learn.microsoft.com/sharepoint/dev/design/design-guidance-overview)
+* [API Docs](https://learn.microsoft.com/javascript/api/sp-application-base)
 
 ## Updates & Feedback
 
@@ -49,7 +49,7 @@ Please see following guidance if you are planning to submit changes on the Share
 
 * [Contribution guidance](https://github.com/SharePoint/sp-dev-docs/blob/master/.github/CONTRIBUTING.md)
 * [How to Create Good Pull Requests](https://github.com/SharePoint/sp-dev-docs/wiki/How-to-Create-Good-Pull-Requests)
-* If you are a Microsoft contributor, please review official guidance from our [internal documentation](https://review.docs.microsoft.com/help/contribute/?branch=master) for docs.microsoft.com contributors
+* If you are a Microsoft contributor, please review official guidance from our [internal documentation](https://review.learn.microsoft.com/help/contribute/?branch=main) for Microsoft Docs contributors
 
 ## Have Fun
 

SECURITY.md

@@ -0,0 +1,41 @@
+<!-- BEGIN MICROSOFT SECURITY.MD V0.0.8 BLOCK -->
+
+## Security
+
+Microsoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, which include [Microsoft](https://github.com/microsoft), [Azure](https://github.com/Azure), [DotNet](https://github.com/dotnet), [AspNet](https://github.com/aspnet), [Xamarin](https://github.com/xamarin), and [our GitHub organizations](https://opensource.microsoft.com/).
+
+If you believe you have found a security vulnerability in any Microsoft-owned repository that meets [Microsoft's definition of a security vulnerability](https://aka.ms/opensource/security/definition), please report it to us as described below.
+
+## Reporting Security Issues
+
+**Please do not report security vulnerabilities through public GitHub issues.**
+
+Instead, please report them to the Microsoft Security Response Center (MSRC) at [https://msrc.microsoft.com/create-report](https://aka.ms/opensource/security/create-report).
+
+If you prefer to submit without logging in, send email to [[email protected]](mailto:[email protected]).  If possible, encrypt your message with our PGP key; please download it from the [Microsoft Security Response Center PGP Key page](https://aka.ms/opensource/security/pgpkey).
+
+You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Additional information can be found at [microsoft.com/msrc](https://aka.ms/opensource/security/msrc). 
+
+Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:
+
+  * Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
+  * Full paths of source file(s) related to the manifestation of the issue
+  * The ___location of the affected source code (tag/branch/commit or direct URL)
+  * Any special configuration required to reproduce the issue
+  * Step-by-step instructions to reproduce the issue
+  * Proof-of-concept or exploit code (if possible)
+  * Impact of the issue, including how an attacker might exploit the issue
+
+This information will help us triage your report more quickly.
+
+If you are reporting for a bug bounty, more complete reports can contribute to a higher bounty award. Please visit our [Microsoft Bug Bounty Program](https://aka.ms/opensource/security/bounty) page for more details about our active programs.
+
+## Preferred Languages
+
+We prefer all communications to be in English.
+
+## Policy
+
+Microsoft follows the principle of [Coordinated Vulnerability Disclosure](https://aka.ms/opensource/security/cvd).
+
+<!-- END MICROSOFT SECURITY.MD BLOCK -->

docs/apis/migration-api-azure-container-and-queue.md

@@ -1,7 +1,7 @@
 ---
 title: SPO provided Migration Azure container and queue
 description: "One of the Main requirement for using our Migration API is the usage of an Azure container as a temporary storage. We now provide a default container that can be used for using the migration API."
-ms.date: 06/28/2022
+ms.date: 07/08/2022
 ms.author: jhendr
 author: JoanneHendrickson
 manager: pamgreen
@@ -10,7 +10,7 @@ ms.localizationpriority: medium
 ---
 # SPO provided Migration Azure container and queue
 
-Microsoft’s Migration API requires the use of an Azure container for temporary storage. To simplify the process, you are now provided with a default container while using the migration API. If you choose, you can still provide your own Azure container.
+Microsoft’s Migration API requires the use of an Azure container for temporary storage. To simplify the process, you are now provided with a default container while using the migration API. To use the provided container you will need to [decorate your traffic correctly](/sharepoint/dev/general-development/how-to-avoid-getting-throttled-or-blocked-in-sharepoint-online#how-to-decorate-your-http-traffic) to avoid throttling. If you choose, you can still provide your own Azure container.
 
 ## Encryption is required
 

docs/apis/migration-api-overview.md

@@ -1,7 +1,7 @@
 ---
 title: "SharePoint Online Import Migration API"
 description: "This article provides in depth information on how to use the SPO Migration API."
-ms.date: 06/28/2022
+ms.date: 12/05/2022
 ms.author: jhendr
 author: JoanneHendrickson
 manager: serdars
@@ -17,7 +17,7 @@ The following API description is based upon use of the SharePoint Client Side Ob
 
 You can find latest version of the SharePoint Online Client Side Object Model (CSOM) package from the [NuGet gallery](https://www.nuget.org/packages/Microsoft.SharePointOnline.CSOM/). Use the ID `Microsoft.SharePointOnline.CSOM`.
 
-> [!Important]
+> [!IMPORTANT]
 > Files larger than 15 GB must now create the required checksum using [QuickXorHash](/onedrive/developer/code-snippets/quickxorhash). We have provided an example [here](#what-is-stored-in-those-azure-blob-containers).
 >
 > The QuickXorHash/Checksum has to be computed for the original file **before** encryption (if the file is being encrypted). This is different from the MD5hash requirement.
@@ -57,7 +57,8 @@ The required permissions are as follows in the Azure Storage API:
 (SharedAccessBlobPermissions.Read | SharedAccessBlobPermissions.List)
 ```
 
-**Note:** The change to enforce Read and List permissions on the SAS token is coming in a future build. Until then it will not be enforced. However, it is a best practice to use these values.
+> [!NOTE]
+> The change to enforce Read and List permissions on the SAS token is coming in a future build. Until then it will not be enforced. However, it is a best practice to use these values.
 
 All files in the container must have at least a single snapshot applied to them to ensure that no file modification is made by the customer during the import. Any file that does not have a snapshot will be skipped during import and have an error thrown, although the job will attempt to continue the import. The import pipeline will use the latest snapshot of the file available at the time of import. The following is an example of the code that might be used to create a snapshot on a file after it is uploaded to Azure Blob Storage:
 
@@ -286,7 +287,7 @@ SPMigrationJobState is an enumeration that tracks possible major states in the i
 
 ## Import Package Structure
 
-Package structure is based on a constrained version of the Content Deployment package schema. Documentation for the original full schema can be found at [docs.microsoft.com](../schema/content-migration-schemas.md). Until published on docs.microsoft.com, the constrained structure can be found in this document in the appendix.
+Package structure is based on a constrained version of the Content Deployment package schema. Documentation for the original full schema can be found in [Content migration schemas](../schema/content-migration-schemas.md). Until published on Microsoft Docs, the constrained structure can be found in this document in the appendix.
 
 |      XML file      |           Schema File           |                                                                                                                                                                                                                                                       Description                                                                                                                                                                                                                                                        |
 | ------------------ | ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
@@ -311,6 +312,38 @@ The **ExportSettings.XML** file is expected to be at the root of the Azure Blob
 
 The main requirement is that the ExportSettings `SiteUrl` value must be populated with a URL consistent with the source URL used for the rest of the import package. In the case of file shares as a source, the URL would be pre-specified to be the source URL in the rest of the package, whereas a package generated through an export operation at a source site would be its original source site collection URL.
 
+#### SourceType required
+
+Beginning January 1, 2023, the SourceType field will be mandatory when calling the Migration API. Starting October 1st, 2022, a warning message will be sent if the field is missing.
+
+Accepted SourceType values:
+
+- AmazonS3
+- AzureStorage
+- Box
+- Dropbox
+- Egnyte
+- FileShare
+- GoogleCloudStorage
+- GoogleDrive
+- MicrosoftStream
+- OneDrive
+- SharePointOnline
+- SharePointOnPremServer
+- Other
+
+When declaring to **Other**, include *DetailedSource* to provide us the detailed information. 
+
+**Example**:
+
+```powershell
+<ExportSettings xmlns="urn:deployment-exportsettings-schema" SiteUrl="https://some site url" FileLocation="some paths" IncludeSecurity="All" SourceType="Other" DetailedSource="My special source type not in the list"> 
+  <ExportObjects> 
+    <DeploymentObject Id="GUID for list" Type="List" ParentId="GUID for web" /> 
+  </ExportObjects> 
+</ExportSettings> 
+```
+
 ### LookupListMap.XML
 
 The **LookupListMap.XML** file, if included, is expected to be at the root of the Azure Blob Store Container defined by the CreateMigrationJob’s azureContainerManifestUri parameter. This optional file is validated using the constrained **DeploymentLookupListMap.XSD**, which has no change from current published [full 2013 package schema](../schema/content-migration-schemas.md).

docs/apis/migration-api-whats-new.md

@@ -1,7 +1,7 @@
 ---
 title: "Migration API What's new"
 description: "Learn about the new features and updates to the Migration API."
-ms.date: 06/28/2022
+ms.date: 11/20/2022
 ms.reviewer: jhendr
 author: JoanneHendrickson
 ms.author: jhendr
@@ -16,6 +16,12 @@ ms.custom: admindeeplinkSPO
 
 Check here to see what features or updates have been added to the Migration API. Here's a summary of what's included.
 
-##  Fixes
+## New requirement
 
-- **Changes to how Import API handles users**. As a response to issues arising from broken OneDrive scenarios when importing duplicate users, the API now blocks and detect duplicate user entries in UserGroup.xml. For details see: [Entering user identifiers in UserGroup.xml](/sharepoint/dev/apis/migration-api-overview#entering-user-identifiers-in-usergroup.xml).
+Beginning January 1, 2023, the SourceType field will be mandatory when calling the Migration API. Starting October 1st, 2022, a warning message will be sent if the field is missing.
+
+To learn more, including examples, see: **[SharePoint Import Migration API - ExportSettings.xml](/sharepoint/dev/apis/migration-api-overview#exportsettingsxml)**
+
+## Fixes
+
+- **Changes to how Import API handles users**. As a response to issues arising from broken OneDrive scenarios when importing duplicate users, the API now blocks and detect duplicate user entries in UserGroup.xml. For details see: [Entering user identifiers in UserGroup.xml](/sharepoint/dev/apis/migration-api-overview#entering-user-identifiers-in-usergroup.xml). 

docs/apis/site-creation-rest.md

@@ -1,7 +1,7 @@
 ---
 title: Create Modern SharePoint Sites using REST
 description: Create and get the status of a new modern SharePoint site by using the REST interface.
-ms.date: 04/06/2022
+ms.date: 12/07/2022
 ms.localizationpriority: high
 ---
 
@@ -44,6 +44,7 @@ body:
     "Lcid": 1033,
     "ShareByEmailEnabled":false,
     "Classification":"Low Business Impact",
+    "SensitivityLabel": "<Your sensitivity label ID>",
     "Description":"Description",
     "WebTemplate":"SITEPAGEPUBLISHING#0",
     "SiteDesignId":"6142d2a0-63a5-4ba0-aede-d9fefca2c767",
@@ -56,6 +57,8 @@ body:
 > [!IMPORTANT]
 > If you use an app-only context to create the site collection the **Owner property is required**. In other cases this is an optional property and if not present will default to the user calling the REST endpoint.
 
+> [!NOTE]
+> The "Classification" parameter only sets the value visible on the site, but doesn't apply the label on the site. Use the new parameter "SensitivityLabel" to actually apply the label on your site collection.
 
 The site design id can be retrieved by using the [Get-SPOSiteDesign](/powershell/module/sharepoint-online/get-spositedesign) (Microsoft SharePoint Online Management Shell) or [Get-PnPSiteDesign](/sharepoint/dev/declarative-customization/site-design-pnppowershell) (PnP PowerShell) cmdlets. If you want to apply an out-of-the-box available site design, use the following values:
 

docs/apis/syntex/rest-applymodel-method.md

@@ -1,18 +1,16 @@
 ---
 title: Batch apply model
+description: Use REST API to apply a document understanding model to one or more libraries.
+ms.date: 09/23/2022
 ms.author: chucked
 author: chuckedmonson
 manager: pamgreen
 ms.reviewer: ssquires
 audience: admin
 ms.topic: reference
-ms.prod: microsoft-365-enterprise
-search.appverid: 
 ms.collection: m365initiative-syntex
 ms.localizationpriority: high
-description: Use REST API to apply a document understanding model to one or more libraries.
 ---
-
 # Batch Apply model
 
 Applies (or syncs) a trained document understanding model to one or more libraries (see [example](rest-applymodel-method.md#examples)).
@@ -72,7 +70,7 @@ None
 |--------|-------|------------|
 |StatusCode|int|The HTTP status code.|
 |ErrorMessage|string|The error message which tells what's wrong when apply the model to the document library.|
-|Publication|MachineLearningPublicationEntityData|It specifies the model info and the target document library.| 
+|Publication|MachineLearningPublicationEntityData|It specifies the model info and the target document library.|
 
 ### MachineLearningPublicationEntityData