Document about directory move

We have tested out the scenario and ensure that StorSimple fully supports Subscription move across directories / tenants.

Here are the steps used for testing –
1.	Created StorSimple resource in a subscription on directory D1.
2.	Registered an appliance to it and created the sub entities – volume containers, volumes, backup policies, backups etc.
3.	Created a new directory D2.
4.	Migrated the subscription to the new directory by clicking “Change directory” option in the subscription details blade and selecting directory D2.
5.	Validated the resource and all its sub entities were working fine after the migration.
6.	Registered a second device and created sub entities.

The above steps ensured a smoke test of all the basic flows related to a StorSimple resource and device, and all passed in completion.

Note: 
•	After the migration it might take some time for the change to propagate, so one could see few transient load errors. Try emptying cache and hard reloading. If needed hit the url - https://login.windows.net/<newTenantId>
•	As long as the subscription remains same all the scenarios will continue to work seamlessly.

Author: anoobbacker

articles/storsimple/storsimple-8000-migrate-classic-azure-portal.md

@@ -13,7 +13,7 @@ ms.devlang: na
 ms.topic: article
 ms.tgt_pltfrm: na
 ms.workload: na
-ms.date: 09/26/2017
+ms.date: 05/21/2018
 ms.author: alkohli
 
 ---
@@ -28,6 +28,7 @@ You may need to move your StorSimple service to a new enrollment or to a new sub
 | An entire subscription (includes StorSimple service and storage accounts) to another enrollment? | Yes       | No       | **Enrollment Transfer**<br>Use :<li>When you  purchase a new Azure commitment under a new agreement.</li><li>You want to migrate all accounts and subscriptions from the old enrollment to the new. This includes all the Azure services under the old subscription.</li> | **Step 1: Open an Azure Enterprise Operation Support ticket.**<li>Go to [http://aka.ms/AzureEnt](http://aka.ms/AzureEnt).</li><li> Select **Enrollment Administration** and then select **Transfer from one enrollment to a new enrollment**.<br>**Step 2: Provide the requested information**<br>Include:<li>source enrollment number</li><li> destination enrollment number</li><li>transfer effective date|
 | StorSimple service from an existing account to a new enrollment?    | Yes       | No       | **Account Transfer**<br>Use:<li>When you do not want a full enrollment transfer.</li><li>You only want to move specific accounts to a new enrollment.</li>| **Step 1: Open an Azure Enterprise Operation Support ticket.**<li>Go to [http://aka.ms/AzureEnt](http://aka.ms/AzureEnt).</li><li>Select **Enrollment Administration** and then select **Transfer an EA Account to a new enrollment**.<br>**Step 2: Provide the requested information**<br>Include:<li>source enrollment number</li><li> destination enrollment number</li><li>transfer effective date|
 | StorSimple service from one subscription to another subscription?      | No        |    Yes         | None, manual process|<li>Migrate data off the StorSimple device.</li><li>Perform a factory reset of the device, this deletes any local data on the device.</li><li>Register the device with the new subscription to a StorSimple Device Manager service.</li><li>Migrate the data back to the device.|
+  |Can I transfer ownership of an Azure subscription to another directory? | Yes       | No       | Associate an existing subscription to your Azure AD directory | Refer [To associate an existing subscription to your Azure AD directory](../active-directory/active-directory-how-subscriptions-associated-directory.md). It might take up to 10 minutes for everything to show up properly.|
 | StorSimple device from one StorSimple Device Manager service to another service in a different region?      | No        | Yes            | None, manual process |Same as above.|
 | Storage account to a new subscription or resource group?     | Yes        | No             |Move storage account to different subscription or resource group |After the move, if the storage account access keys are updated, the user will need to configure the access keys manually for the migrated storage account through the StorSimple Device Manager service.|
 | Classic storage account to an Azure Resource Manager storage account      | Yes        | No             |Migrate from classic to Azure Resource Manager |<li>For detailed instructions on how to migrate a storage account from classic to Azure Resource Manager, go to [Migrate a classic storage account](../virtual-machines/windows/migration-classic-resource-manager-ps.md#step-62-migrate-a-storage-account).</li><li> If the storage account access keys are updated after migration, the user will need to synchronize the access keys for the migrated storage account through the StorSimple Device Manager service. This is to ensure the StorSimple devices continue to function normally and are able to tier primary/backup data to Azure. For detailed instructions on synchronizing access keys, go to [Rotation workflow](storsimple-8000-manage-storage-accounts.md#key-rotation-of-storage-accounts).</li><li> In the case of a StorSimple Cloud Appliance, if the classic storage account is migrated but the underlying virtual machine still stays in classic, the appliance should function properly. If the underlying virtual machine for the cloud appliance is migrated, then the deactivate and delete functionality will not work.</li><li> You must create a new StorSimple Cloud Appliances in the Azure portal and then fail over from the older cloud appliances. You cannot create a StorSimple Cloud Appliance in the new Azure portal using a classic storage account, they need to have an Azure Resource Manager storage account. For more information, go to [Deploy and manage a StorSimple Cloud Appliance](storsimple-8000-cloud-appliance-u2.md).</li>|Same as above.|