2 ms·
That could likely be the case from the error message. It's still a problem MS should solve. If they don't have a good protection from azuread abuse and no appea
by viraptor 4y ago
That could likely be the case from the error message. It's still a problem MS should solve. If they don't have a good protection from azuread abuse and no appeal, that's an issue on its own.
- paranoidrobot 4y ago> It's still a problem MS should solve. Microsoft's ID systems has been fucked for ages. They are either incapable of fixing it, or just don't give a damn. About, oh, 8 years ago at a previous company, we signed up for and used AzureAD on a trial. It immediately broke our ability for staff to create a Microsoft account with our domain and a bunch of business processes that depended on those. Our account rep at the time wasn't able to get us any help, and despite cancelling the trial the domain remained locked to Azure AD. Microsoft wasn't interested in fixing it, only signing us up for AzureAD and O365.