Merge branch 'master' into patch-2

Author: VesaJuvonen

README.md

@@ -15,6 +15,12 @@ We’ll also monitor [#spfx](http://sharepoint.stackexchange.com/tags/spfx/), [#
 You can also tweet / follow [@officedev](https://twitter.com/officedev) or [@officedevpnp](https://twitter.com/officedevpnp).
 
 ## SharePoint Framework Releases
+* **September 5, 2018**
+   * **SPFx v1.6** - [See the release notes here](https://github.com/SharePoint/sp-dev-docs/wiki/SharePoint-Framework-v1.6-release-notes)
+
+* **June 26, 2018**
+   * **SPFx v1.5.1** - [See the release notes here](https://github.com/SharePoint/sp-dev-docs/wiki/Release-Notes-for-SPFx-Package-Version-1.5.1)
+   
 * **June 5, 2018**
    * **SPFx v1.5** - [See the release notes here](https://github.com/SharePoint/sp-dev-docs/wiki/Release-Notes-for-SharePoint-Framework-Package-v1.5)
 

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

@@ -223,17 +223,17 @@ Get-PnPApp -Scope Tenant
 
 ## Office 365 CLI commands to add, deploy, and manage SharePoint apps cross-platform
 
-Using the [Office 365 CLI](https://sharepoint.github.io/office365-cli?utm_source=msft_docs&utm_medium=page&utm_campaign=Application+Lifecycle+Management+ALM+APIs), you can automate deploying, publishing, installing, upgrading, and retracting your apps. The Office 365 CLI is a cross-platform command-line interface that can be used on any platform, including Windows, MacOS, and Linux. To learn more about these commands, see the following sections.
+Using the [Office 365 CLI](https://pnp.github.io/office365-cli?utm_source=msft_docs&utm_medium=page&utm_campaign=Application+Lifecycle+Management+ALM+APIs), you can automate deploying, publishing, installing, upgrading, and retracting your apps. The Office 365 CLI is a cross-platform command-line interface that can be used on any platform, including Windows, MacOS, and Linux. To learn more about these commands, see the following sections.
 
 ### Add and publish your app to the app catalog
 
-Adding your app (.sppkg file, .app file) to the tenant app catalog is a prerequisite to making your app available for use on your SharePoint sites. Use the [add](https://sharepoint.github.io/office365-cli/cmd/spo/app/app-add/?utm_source=msft_docs&utm_medium=page&utm_campaign=Application+Lifecycle+Management+ALM+APIs) command to do this:
+Adding your app (.sppkg file, .app file) to the tenant app catalog is a prerequisite to making your app available for use on your SharePoint sites. Use the [add](https://pnp.github.io/office365-cli/cmd/spo/app/app-add/?utm_source=msft_docs&utm_medium=page&utm_campaign=Application+Lifecycle+Management+ALM+APIs) command to do this:
 
 ```shell
 spo app add --filePath ./spfx.sppkg
 ```
 
-Once added, you need to continue with publishing your app, effectively making the app available to be used by the users of your tenant. Use the [deploy](https://sharepoint.github.io/office365-cli/cmd/spo/app/app-deploy/?utm_source=msft_docs&utm_medium=page&utm_campaign=Application+Lifecycle+Management+ALM+APIs) command to do this:
+Once added, you need to continue with publishing your app, effectively making the app available to be used by the users of your tenant. Use the [deploy](https://pnp.github.io/office365-cli/cmd/spo/app/app-deploy/?utm_source=msft_docs&utm_medium=page&utm_campaign=Application+Lifecycle+Management+ALM+APIs) command to do this:
 
 ```shell
 spo app deploy --id <app id> --skipFeatureDeployment
@@ -247,7 +247,7 @@ spo app deploy --id <app id> --skipFeatureDeployment
 
 ### Remove the app from the app catalog
 
-You may want to remove an app that you added earlier, and you can do this by using the [remove](https://sharepoint.github.io/office365-cli/cmd/spo/app/app-remove/?utm_source=msft_docs&utm_medium=page&utm_campaign=Application+Lifecycle+Management+ALM+APIs) command:
+You may want to remove an app that you added earlier, and you can do this by using the [remove](https://pnp.github.io/office365-cli/cmd/spo/app/app-remove/?utm_source=msft_docs&utm_medium=page&utm_campaign=Application+Lifecycle+Management+ALM+APIs) command:
 
 ```shell
 spo app remove --id <app id>
@@ -256,21 +256,21 @@ spo app remove --id <app id>
 
 ### Use apps on your site
 
-After the app is added to the app catalog and published, you can install the app to your site by using the [install](https://sharepoint.github.io/office365-cli/cmd/spo/app/app-install/?utm_source=msft_docs&utm_medium=page&utm_campaign=Application+Lifecycle+Management+ALM+APIs) command:
+After the app is added to the app catalog and published, you can install the app to your site by using the [install](https://pnp.github.io/office365-cli/cmd/spo/app/app-install/?utm_source=msft_docs&utm_medium=page&utm_campaign=Application+Lifecycle+Management+ALM+APIs) command:
 
 ```shell
 spo app install --id <app id> --siteUrl <url>
 ```
 
 
-To upgrade the app, use the [upgrade](https://sharepoint.github.io/office365-cli/cmd/spo/app/app-upgrade/?utm_source=msft_docs&utm_medium=page&utm_campaign=Application+Lifecycle+Management+ALM+APIs) command:
+To upgrade the app, use the [upgrade](https://pnp.github.io/office365-cli/cmd/spo/app/app-upgrade/?utm_source=msft_docs&utm_medium=page&utm_campaign=Application+Lifecycle+Management+ALM+APIs) command:
 
 ```shell
 spo app upgrade --id <app id> --siteUrl <url>
 ```
 
 
-To uninstall the app from your site, use the [uninstall](https://sharepoint.github.io/office365-cli/cmd/spo/app/app-uninstall/?utm_source=msft_docs&utm_medium=page&utm_campaign=Application+Lifecycle+Management+ALM+APIs) command:
+To uninstall the app from your site, use the [uninstall](https://pnp.github.io/office365-cli/cmd/spo/app/app-uninstall/?utm_source=msft_docs&utm_medium=page&utm_campaign=Application+Lifecycle+Management+ALM+APIs) command:
 
 ```shell
 spo app uninstall --id <app id> --siteUrl <url>
@@ -282,14 +282,14 @@ spo app uninstall --id <app id> --siteUrl <url>
 
 
 ### List and get apps in the app catalog
-You can see what apps have been added to the app catalog by using the [list](https://sharepoint.github.io/office365-cli/cmd/spo/app/app-list/?utm_source=msft_docs&utm_medium=page&utm_campaign=Application+Lifecycle+Management+ALM+APIs) command:
+You can see what apps have been added to the app catalog by using the [list](https://pnp.github.io/office365-cli/cmd/spo/app/app-list/?utm_source=msft_docs&utm_medium=page&utm_campaign=Application+Lifecycle+Management+ALM+APIs) command:
 
 ```shell
 spo app list
 ```
 
 
-You can get a single app's details by using the [get](https://sharepoint.github.io/office365-cli/cmd/spo/app/app-get/?utm_source=msft_docs&utm_medium=page&utm_campaign=Application+Lifecycle+Management+ALM+APIs) command:
+You can get a single app's details by using the [get](https://pnp.github.io/office365-cli/cmd/spo/app/app-get/?utm_source=msft_docs&utm_medium=page&utm_campaign=Application+Lifecycle+Management+ALM+APIs) command:
 
 ```shell
 spo app get --id <app id>

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

@@ -0,0 +1,64 @@
+---
+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.

docs/apis/migration-api-encryption.md

@@ -0,0 +1,80 @@
+---
+title: OneDrive for Business and SharePoint Online Migration API – Encryption
+ms.author: jhendr
+author: JoanneHendrickson
+manager: pamgreen
+ms.date: 6/20/2018
+description: "How to pass encrypted content at rest to the API securely."
+---
+
+# OneDrive for Business and SharePoint Online Migration API encryption
+
+Using the Migration API requires a temporary storage container in Azure. This Azure container is already only openable by someone having a SAS key access to the container. The gGoal of this feature is to allow to pass eEncrypted content at rest to the API meaning that even if a malicious user has access to the Container he won’t be able to use its content.
+
+## What is stored in the Azure blob container
+
+The Migration API requires the Azure Container for content passing and also for log and queue reporting back. It can be split down as a summary into those buckets:
+
+Content
+
+- Files
+- Manifest
+    - Metadata
+    - Permissions
+    - List items
+    - Taxonomy
+    - Logs (created by SharePoint Online to report back on the migration results)
+- Queue
+    - Real time reportig on the progress
+
+## What is the encryption feature?
+
+When using the encryption parameter, everything listed above will be encrypted at rest and the key will need to be preserved in order to read the logs and the real time progress. 
+The main benefits is making the content useless for a malicious user who would manage to breach into the Azure container. 
+
+This comes with a small cost of performance. This feature is optional when using the API and it is recommended to only use it for the most confidential information since it does reduce the speed of the migration by a small portion. Microsoft destroys the key once the migration job is finished and there is no way to recover the key if lost, not even from support.
+
+## As a 3rd party developer how do I take advantage of the Encryption feature?
+
+### Calling the API
+
+The method for calling the Migration Job has a different name and an additional parameter at the end. The new name is: `CreateMigrationJobEncrypted`
+
+The new parameter is: `EncryptionOption`
+
+For now, it only supports receiving an AES256CBC Encryption Key.
+
+Example:
+
+```csharp
+    public Guid CreateMigrationJobEncrypted(
+        Guid gWebId,
+        string azureContainerSourceUri,
+        string azureContainerManifestUri,
+        string azureQueueReportUri,
+        EncryptionOption AES256CBCKey)
+```
+
+## Extra requirement
+
+For the encryption, each file must be encrypted and have an IV assigned to it. The encryption method should follow the AES CBC 256 Standard. The IV should be different for every file including the manifests in the package and should be stored as a property on each files. 
+
+- Name = [IV] 
+- Value = [Base64encoded byte array of the IV]
+
+## Reading the queue when encrypted
+
+When using the encryption option, the messages in the queue will also get encrypted.
+
+It is important to remember the Job ID. Without the specific key used for the job, you won’t be able to read the message back.
+
+Here is the JSON content in the queue message
+
+```json
+{"Label", "Encrypted"},
+{"JobId", "[JobId value]"},
+{"IV", "[IV value in base64format]"},     
+{"Content", "[encrypted message in base64string]"}  
+```
+
+Once the messages are decrypted, they will be the same as the API without encryption.

docs/apis/migration-api-handling-trottling.md

@@ -0,0 +1,51 @@
+---
+title: "Running Migrations into OneDrive and SharePoint Online: Handling Throttling "
+ms.author: jhendr
+author: JoanneHendrickson
+manager: pamgreen
+ms.date: 6/10/2018
+ms.topic: article
+description: "Migration is critical for SPO and is prioritized alongside service availability."
+---
+
+# Running Migrations into OneDrive and SharePoint Online: Throttling
+
+This document is intended for ISVs migrating content into OneDrive and SharePoint only.
+
+## Context and Expectations Setting
+
+Migration is critical for SPO and is prioritized alongside service availability. When we detect that service availability may be threatened, 429 response codes are sent back to protect the experience of end users.  
+
+429 is a normal part of any well-functioning cloud system; the expectation is that background tasks will get 429s and all background task callers (both ISVs and Microsoft apps) should ride through them without direct customer impact to their own end users.
+ 
+The number of 429s sent back is a function of the current load on the farm, as well as other tenant/farm level variables. Therefore, it is important to focus on migration throughput rather than the number of 429s themselves.  
+
+Set expectations with customers:
+
+- Expect to create and manage migration efforts at any time
+- Expect content migration throughput to be higher during off-peak times and lower during peak times.  
+
+Overall throughput over the duration of a day still aligns with our public documentation here.
+
+## Best Practices
+
+Below are the key best practices we recommend migration vendors follow.  
+
+**Interactive flag:**<br>Include an *interactive flag* in your user agent string for interactive calls such as user login, launch jobs, etc. For example:   `ISV|VendorName|AppName/Version|Interactive` <br>
+
+We allow 300 calls every 5 minutes for handling small migrations and site management that customers expect to complete interactively.
+
+> [!NOTE]
+>  Once you have implemented Interactive flag for the system to pick that cue, it may not be instantaneous; allow a few days for it to take effect. 
+ 
+**Retry value**:<br>Use the retry value in the http header of the 429 message and do not exponential back-off. 
+ 
+**429:**<br>Do not handle 429 as an error condition displayed to the user.  When 429 does occur, handle it as a background task retry and do not prompt users to contact support.
+
+- If users cannot login or if jobs are not progressing, please escalate.
+- If you are seeing over 30% of requests getting 429 over 30 minutes, please escalate.
+ 
+**Throughput:**<br>Expect throughput to be lower during peak hours as opposed to off-peak hours. Generally, nights and weekends in the customer’s time zone (the time zone of the region where their SPO tenant is setup) are off-peak.  Customers should be encouraged to move migration to off-peak hours if possible.
+
+-  If throughput during peak hours is an order of magnitude worse than off-peak hours, that should be escalated.
+