Migration to self-service deployments
Important
This content is archived and is not being updated. For the latest documentation, see Microsoft Dynamics 365 product documentation. For the latest release plans, see Dynamics 365 and Microsoft Power Platform release plans.
| Enabled for | Public preview | General availability |
|---|---|---|
| Admins, makers, or analysts, automatically | - |  Oct 1, 2019 |
Feature details
Microsoft enabled self-service deployments for new customers in the fall of 2018. Starting in summer 2019, Microsoft coordinates with customers to migrate their environments to self-service deployment. The default sandbox is migrated first. Two notification emails are also sent. The first email is a 30-day advance notice, and the second email is a reminder notice sent five days before the scheduled migration. Migration can be rescheduled through an online form in extenuating circumstances.
Preparing for migration
Customers should start updating their environments on the current online service with combined deployable packages going forward. This was always the recommended best practice and will now be enforced.
What's new or changed
Customers will no longer have direct access to server admin credentials on Tier 2+ environments. They will continue to have access to Azure SQL Database and will be able to connect using just-in-time access from Lifecycle Services (LCS).
Customers will no longer have access to remote desktop credentials on Tier 2+ environments. All operations needing remote desktop access have been made available as self-service operations in LCS.