Make the E5 Developer Subscription Available To Existing Tenant!
The requirement to activate a developer subscription to create a new tenant is very unreasonable. For example, I already have my own tenant, and bind a custom domain name for testing. Why should I be asked to create a new tenant to participate in the test of new subscription? Developer subscriptions are not free trials, and no one wants to have many abandoned tenants and accounts.
Thanks to all of you for your feedback. There are very specific technical reasons why we can’t give you what you want. The developer subscription is a special type of trial that prevents this kind of upgrade. Our best solution is what we built ( to delete and replace). We talked to many customers in the process of looking at our options and they were OK with this approach.
A saw that the documentation is now updated. Very interesting, when I sign in to https://developer.microsoft.com/office/profile I have no subscriptions, so there is nothing to replace. Wonder would that result in a situation that I actually will be able to have both Office 365 E3 and Microsoft 365 E5 in two different tenants. Hmm, interesting. Maybe its worth the work to move to the new tenant if I get to keep the old tenant as an additional lab.
There is an ongoing survey, fill it out and complain as I did.
Jimmy L commented
You would think it would be a check box or something simple. Don't understand why it is so hard to have this. Someone with Microsoft should be able to just change the license automatically for all developer subscriptions.
Yes - exactly that. An in-place upgrade to ensure current policies, settings and security boundaries are maintained. Surely - it would be trivial to simply add the E5, and pull away the E3?
Jimmy L commented
I think he is saying, how can I migrate from a Developer E3 to Developer E5. We have the would like to do the same. In the notes it says a way will be provided for existing Dev E3 users to move to E5 and I have not found a way for us to do that.
Adminmikeald (Admin, Microsoft) commented
We don't allow you to use your existing M365 subscriptions in the dev program because we have specific terms and conditions that apply to our subscriptions and we need to have a consistent environment to ensure tools like sample data packs can be installed.
Can you tell us why it is such a pain point to create your own sandbox subscription through our program?