Forum Discussion
CDX - Terms Of Use Last Updated - March 12, 2024
I'm not a big fan of these 2 limitations in the terms of use:
- CDX tenants have an administrative user that should not be deleted or altered in any way.
- External domains are not to be connected to CDX tenants.
For the 1st, I want to set my own password on the admin@ account. What's so wrong with that? You could reset it if you really need/want to get in there. This is not fair.
For the 2nd, of course we want to test with custom domains! This is again no fair.
The other thing - I've already added my custom domain in my VSE Azure Subscription which I've associated to my CDX tenant directory. In there, I'm testing out SMTP as a Service via Azure Communication Services. Again, of course I want to use my own custom domain, with DKIM, DMARC, SPF, etc. This is completely reasonable.
Today I login to CDX to see if my ability to request renewal of my renewable tenant is available yet, and I can't even get in without accepting the new terms. But it says:
"
Violations of the CDX Terms of Use will result in the immediate deprecation of tenants as well as access to CDX without notice.
JeremyTBradshaw Mandatory Microsoft Entra multifactor authentication (MFA) - Microsoft Entra ID | Microsoft Learn
Kind of silly to think the terms used to prevent and threaten against MFA, let alone even a password reset. Now MFA is mandatory for admins. Nice to see the common sense come back around.
4 Replies
- JeremyTBradshawIron Contributor
JeremyTBradshaw Mandatory Microsoft Entra multifactor authentication (MFA) - Microsoft Entra ID | Microsoft Learn
Kind of silly to think the terms used to prevent and threaten against MFA, let alone even a password reset. Now MFA is mandatory for admins. Nice to see the common sense come back around.
- DavidY-IMPCopper ContributorI agree with both Jeremy and Mike's points, particularly around the removal of custom domains. This brings a number of limitations for what can be tested with CDX tenants that used to be possible and does not allow for real world use case testing. I am not sure why this limitation would be introduced, but I strongly recommend for that decision to be re-evaluated.
- MikeMasonIMPCopper ContributorI concur, what's the point of having test environments if we can't do proper testing? As a Microsoft partner we would expect to have test environments that would allow us a little more free reign without having the cuffs on. Having the ability to control our own admin passwords and our own custom domains is an absolute must.
- JeremyTBradshawIron ContributorThanks Mike. I will also add a comment to further justify custom domains.. It is the fact that some CDX tenants are A) 1-year, and B) renewable. Considering that, it should be assumed that some partners are going to fire-up long-lived CDX tenants, in which case custom domains become more and more likely to be something we want to test with. I can understand not letting custom domains into a 30-day or non-renewable CDX tenant. But 1-year + renewable (at the very least) should be left alone from this limitation.