Adding intl metadata localization_priority to US source markdown files (SharePoint#3249)

Author: OfficeGSX

docs/apis/alm-api-for-spfx-add-ins.md

@@ -1,128 +1,129 @@
----
-title: Create SharePoint Communication site using REST
-description: Create and get the status of a new modern SharePoint Communication site by using the REST interface.
-ms.date: 4/19/2018
-ms.prod: sharepoint
----
-
-# Create SharePoint Communication site using REST
-
-This topic assumes that you are already familiar with the following topics: 
-
-- [Get to know the SharePoint REST service](../sp-add-ins/get-to-know-the-sharepoint-rest-service.md)
-- [Complete basic operations using SharePoint REST endpoints](../sp-add-ins/complete-basic-operations-using-sharepoint-rest-endpoints.md)
-
-This topic does not provide code snippets.
-
-The following REST commands are available for creating a modern SharePoint Communication site:
-
-- **Create**. Create a new SharePoint Communication site.
-- **Status**. Get the status of a SharePoint Communication site.
-
-The URL for Communication site REST commands is based on `_api/sitepages/communicationsite`. For example, these are the endpoints for the REST commands listed earlier:
-
-- `http:///_api/sitepages/communicationsite/create`
-- `http:///_api/sitepages/communicationsite/status`
-
-## Create Communication site
-
-```json
-url: /_api/sitepages/communicationsite/create
-method: POST
-body:
-{
-   "request":{
-      "__metadata":{
-         "type":"SP.Publishing.CommunicationSiteCreationRequest"
-      },
-      "AllowFileSharingForGuestUsers":false,
-      "Classification":"LBI",
-      "Description":"Description",
-      "SiteDesignId":"6142d2a0-63a5-4ba0-aede-d9fefca2c767",
-      "Title":"Comm Site 1",
-      "Url":"https://vesku.sharepoint.com/sites/commsite132",
-      "lcid":1033
-   }
-}
-```
-
-> [!IMPORTANT]
-> The `lcid` parameter is not currently supported with this API. You can currently only create English sites. 
-
-New in this API is the concept of `SiteDesignID`. Much like the in-product site creation flow, the `SiteDesignID` parameter maps to the included site designs. They are:
-
-- Topic: null
-- Showcase: 6142d2a0-63a5-4ba0-aede-d9fefca2c767
-- Blank: f6cc5403-0d63-442e-96c0-285923709ffc
-
-### Response
-
-If successful, this method returns a `200, OK` response code and simple JSON object in the response body with the following details.
-
-```json
-{
-  "d":{
-      "Create":{
-           "__metadata":{"type":"SP.Publishing.CommunicationSiteCreationResponse"},
-          "SiteStatus":2,
-          "SiteUrl":"https://contoso.sharepoint.com/sites/comm1"
-      }
-  }
-}
-```
-
-
-## Get Communication site status
-
-The REST API for getting the status of a modern SharePoint Communication site:
-
-```json
-url: /_api/sitepages/communicationsite/status?url='https%3A%2F%2Fcontoso.sharepoint.com%2Fsites%2Fcomm1'
-method: GET
-body: none
-```
-
-### Response
-
-If successful, this method returns a `200, OK` response code and simple JSON object in the response body with the following details.
- 
-If the site exists, the response returns the site status and site URL:
-
-```json
-{
-  "d":{
-      "Status":{
-           "__metadata":{"type":"SP.Publishing.CommunicationSiteCreationResponse"},
-          "SiteStatus":2,
-          "SiteUrl":"https://contoso.sharepoint.com/sites/comm1"
-      }
-  }
-}
-```
-
-<br/>
-
-If the site does not exist, the response returns a site status of 0 with no URL.
-
-```json
-{
-  "d":{
-      "Status":{
-           "__metadata":{"type":"SP.Publishing.CommunicationSiteCreationResponse"},
-          "SiteStatus":0,
-          "SiteUrl":
-      }
-  }
-}
-```
-
-The full set of values for SiteStatus are as follows:
-
-+ `0` - Not Found.  The site doesn't exist.
-+ `1` - Provisioning.  The site is currently being provisioned.
-+ `2` - Ready.  The site has been created.
-+ `3` - Error.  An error occurred while provisioning the site.
-
-## See also
-
-- [Get to know the SharePoint REST service](../sp-add-ins/get-to-know-the-sharepoint-rest-service.md)
+---
+title: Create SharePoint Communication site using REST
+description: Create and get the status of a new modern SharePoint Communication site by using the REST interface.
+ms.date: 4/19/2018
+ms.prod: sharepoint
+localization_priority: Priority
+---
+
+# Create SharePoint Communication site using REST
+
+This topic assumes that you are already familiar with the following topics: 
+
+- [Get to know the SharePoint REST service](../sp-add-ins/get-to-know-the-sharepoint-rest-service.md)
+- [Complete basic operations using SharePoint REST endpoints](../sp-add-ins/complete-basic-operations-using-sharepoint-rest-endpoints.md)
+
+This topic does not provide code snippets.
+
+The following REST commands are available for creating a modern SharePoint Communication site:
+
+- **Create**. Create a new SharePoint Communication site.
+- **Status**. Get the status of a SharePoint Communication site.
+
+The URL for Communication site REST commands is based on `_api/sitepages/communicationsite`. For example, these are the endpoints for the REST commands listed earlier:
+
+- `http:///_api/sitepages/communicationsite/create`
+- `http:///_api/sitepages/communicationsite/status`
+
+## Create Communication site
+
+```json
+url: /_api/sitepages/communicationsite/create
+method: POST
+body:
+{
+   "request":{
+      "__metadata":{
+         "type":"SP.Publishing.CommunicationSiteCreationRequest"
+      },
+      "AllowFileSharingForGuestUsers":false,
+      "Classification":"LBI",
+      "Description":"Description",
+      "SiteDesignId":"6142d2a0-63a5-4ba0-aede-d9fefca2c767",
+      "Title":"Comm Site 1",
+      "Url":"https://vesku.sharepoint.com/sites/commsite132",
+      "lcid":1033
+   }
+}
+```
+
+> [!IMPORTANT]
+> The `lcid` parameter is not currently supported with this API. You can currently only create English sites. 
+
+New in this API is the concept of `SiteDesignID`. Much like the in-product site creation flow, the `SiteDesignID` parameter maps to the included site designs. They are:
+
+- Topic: null
+- Showcase: 6142d2a0-63a5-4ba0-aede-d9fefca2c767
+- Blank: f6cc5403-0d63-442e-96c0-285923709ffc
+
+### Response
+
+If successful, this method returns a `200, OK` response code and simple JSON object in the response body with the following details.
+
+```json
+{
+  "d":{
+      "Create":{
+           "__metadata":{"type":"SP.Publishing.CommunicationSiteCreationResponse"},
+          "SiteStatus":2,
+          "SiteUrl":"https://contoso.sharepoint.com/sites/comm1"
+      }
+  }
+}
+```
+
+
+## Get Communication site status
+
+The REST API for getting the status of a modern SharePoint Communication site:
+
+```json
+url: /_api/sitepages/communicationsite/status?url='https%3A%2F%2Fcontoso.sharepoint.com%2Fsites%2Fcomm1'
+method: GET
+body: none
+```
+
+### Response
+
+If successful, this method returns a `200, OK` response code and simple JSON object in the response body with the following details.
+ 
+If the site exists, the response returns the site status and site URL:
+
+```json
+{
+  "d":{
+      "Status":{
+           "__metadata":{"type":"SP.Publishing.CommunicationSiteCreationResponse"},
+          "SiteStatus":2,
+          "SiteUrl":"https://contoso.sharepoint.com/sites/comm1"
+      }
+  }
+}
+```
+
+<br/>
+
+If the site does not exist, the response returns a site status of 0 with no URL.
+
+```json
+{
+  "d":{
+      "Status":{
+           "__metadata":{"type":"SP.Publishing.CommunicationSiteCreationResponse"},
+          "SiteStatus":0,
+          "SiteUrl":
+      }
+  }
+}
+```
+
+The full set of values for SiteStatus are as follows:
+
++ `0` - Not Found.  The site doesn't exist.
++ `1` - Provisioning.  The site is currently being provisioned.
++ `2` - Ready.  The site has been created.
++ `3` - Error.  An error occurred while provisioning the site.
+
+## See also
+
+- [Get to know the SharePoint REST service](../sp-add-ins/get-to-know-the-sharepoint-rest-service.md)

docs/apis/communication-site-creation-rest.md

@@ -1,64 +1,65 @@
----
-title: SPO provided Migration Azure container and queue
-ms.author: jhendr
-author: JoanneHendrickson
-manager: pamgreen
-ms.date: 6/20/2018
-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."
----
-
-# 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.
-
-## Encryption is required
-
-For the Migration API to accept a Migration Job coming from a SPO provided Azure container, the data needs to be encrypted at rest. The customer is still allowed to provide their own Azure account if they prefer to not use encryption.
-
-##  Advantages
-
-|Advantage|Description|
-|:-----|:-----|
-|Cost of Azure container goes to SPO|Since we are providing the containers, those containers are now part of the basic SharePoint online Offering. Every tenant who signs up for SharePoint Online will get this for free).|
-|Containers and queues are unique per request and not reused|Once a container is given to a customer this container will not be reused or shared.|
-|Containers and queue are automatically deleted|As per the standard SharePoint Online Compliance, we will destroy the container within 30 to 90 days automatically.|
-|Containers and queues are in the customer’s datacenter ___location|We make sure to provision containers that are in the same physical ___location than their SharePoint online tenant.| 
-|They are obtainable programmatically|There is no need to interact with Azure unless the user chooses.
-
-## How to use it
-
-### Getting Containers
-
-```csharp
-    public SPProvisionedMigrationContainersInfo ProvisionMigrationContainers()
-```
-
-The call will return an object that contains two strings containing two SAS tokens for accessing the two required containers and a byte array for the AES256CBC encryption. 
-
-This key will need to be used when encrypting the data. We forget the key once we give it out, therefore you must keep it to pass it again for the Submit Migration Job call.
-
-```csharp
-    Uri DataContainerUri 
-
-    Uri MetadataContainer Uri
-
-    byte[] EncryptionKey 
-```
-
-### Getting Queue
-
-```csharp
-    public SPProvisionedMigrationQueueInfo ProvisionMigrationQueue()
-```
-
-This method will return a string containing the SAS token for accessing the Azure queue.
-
-The queue can be reused across multiple migration jobs so this call should not be that frequently as the `SPProvisionedMigrationContainersInfo()` call.
-
-```csharp
-    Uri JobQueueUri
-```
-
-### After getting the Container and the Queue:
-
-Once those calls have been made, the rest of the flow remains the same for using the Migration API.
+---
+title: SPO provided Migration Azure container and queue
+ms.author: jhendr
+author: JoanneHendrickson
+manager: pamgreen
+ms.date: 6/20/2018
+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."
+localization_priority: Normal
+---
+
+# 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.
+
+## Encryption is required
+
+For the Migration API to accept a Migration Job coming from a SPO provided Azure container, the data needs to be encrypted at rest. The customer is still allowed to provide their own Azure account if they prefer to not use encryption.
+
+##  Advantages
+
+|Advantage|Description|
+|:-----|:-----|
+|Cost of Azure container goes to SPO|Since we are providing the containers, those containers are now part of the basic SharePoint online Offering. Every tenant who signs up for SharePoint Online will get this for free).|
+|Containers and queues are unique per request and not reused|Once a container is given to a customer this container will not be reused or shared.|
+|Containers and queue are automatically deleted|As per the standard SharePoint Online Compliance, we will destroy the container within 30 to 90 days automatically.|
+|Containers and queues are in the customer’s datacenter ___location|We make sure to provision containers that are in the same physical ___location than their SharePoint online tenant.| 
+|They are obtainable programmatically|There is no need to interact with Azure unless the user chooses.
+
+## How to use it
+
+### Getting Containers
+
+```csharp
+    public SPProvisionedMigrationContainersInfo ProvisionMigrationContainers()
+```
+
+The call will return an object that contains two strings containing two SAS tokens for accessing the two required containers and a byte array for the AES256CBC encryption. 
+
+This key will need to be used when encrypting the data. We forget the key once we give it out, therefore you must keep it to pass it again for the Submit Migration Job call.
+
+```csharp
+    Uri DataContainerUri 
+
+    Uri MetadataContainer Uri
+
+    byte[] EncryptionKey 
+```
+
+### Getting Queue
+
+```csharp
+    public SPProvisionedMigrationQueueInfo ProvisionMigrationQueue()
+```
+
+This method will return a string containing the SAS token for accessing the Azure queue.
+
+The queue can be reused across multiple migration jobs so this call should not be that frequently as the `SPProvisionedMigrationContainersInfo()` call.
+
+```csharp
+    Uri JobQueueUri
+```
+
+### After getting the Container and the Queue:
+
+Once those calls have been made, the rest of the flow remains the same for using the Migration API.