3 ms·

Google isn't the only one. Somebody must have used my domain to sign up for a Microsoft Teams something for some reason and NOBODY in my company can find out w

by ROFISH 6y ago

Google isn't the only one. Somebody must have used my domain to sign up for a Microsoft Teams something for some reason and NOBODY in my company can find out who or how. Microsoft is absolutely unhelpful in this regard, trying to activate our domain for Office Teams or whatever. Microsoft says it's for "security" reasons; but as CIO of a 50+ person org I should have some override on that in the event of erroneous signups. I don't even need to access old content because none of us has used the service at all. Just delete the old domain. For all I know it was a troll signup. I've since just forced my team to use Google Docs/Sheets because Microsoft is being so unhelpful that they won't even let us give them money, lol.

WrtCdEvrydy 6y ago
To be honest, the alternative is someone being able to delete your organization on Teams. I kinda wish you could do like google analytics makes you do to validate your URL (add a DNS record)
- rootsudo 6y ago
  You can, the whole point is verifying the domain in O365 by modifying the PTR record and CNAME so that the o365 panel will see it is yours. Support should've been able to remove it, I know I was able to do it on escalation cases when I was on Fast Track. I know that the "ambassadors" are really next to worthless, and if you do not have premier or a TAM on your account, you are really SOL on O365/M365/Microsoft products, you need to email the ambassadors managers, continually, and then go up the ladder, if needbe, to the product manager of that support team and just keep doing it. It really sucks. But the reason you couldn't add your domain is 99% most likely someone added and verified it. There are tools on the backend (most easiest Viewpoint) and then billing (CMAT) that can verify if domain is added.
shiftpgdn 6y ago
We had this problem with O365 a few years ago. Someone had signed up using our company domain and it created a mountain of heart ache. If I recall correctly we had to make a second domain our primary and then setup aliases for everything.
hirsin 6y ago
https://docs.microsoft.com/en-us/azure/active-directory/users-groups-roles/domains-admin-takeover https://docs.microsoft.com/en-us/azure/active-directory/user... It's still not well supported for "external" takeover but it's disappointing that your support queue didn't point you to the docs on this. Per below though, if someone made it "managed" through DNS verification, yeah, that's hard. Keywords to search in this scenario "viral admin takeover AAD"

by ROFISH 6y ago

WrtCdEvrydy 6y ago

To be honest, the alternative is someone being able to delete your organization on Teams. I kinda wish you could do like google analytics makes you do to validate your URL (add a DNS record)

rootsudo 6y ago
You can, the whole point is verifying the domain in O365 by modifying the PTR record and CNAME so that the o365 panel will see it is yours. Support should've been able to remove it, I know I was able to do it on escalation cases when I was on Fast Track. I know that the "ambassadors" are really next to worthless, and if you do not have premier or a TAM on your account, you are really SOL on O365/M365/Microsoft products, you need to email the ambassadors managers, continually, and then go up the ladder, if needbe, to the product manager of that support team and just keep doing it. It really sucks. But the reason you couldn't add your domain is 99% most likely someone added and verified it. There are tools on the backend (most easiest Viewpoint) and then billing (CMAT) that can verify if domain is added.

shiftpgdn 6y ago

We had this problem with O365 a few years ago. Someone had signed up using our company domain and it created a mountain of heart ache. If I recall correctly we had to make a second domain our primary and then setup aliases for everything.

hirsin 6y ago

https://docs.microsoft.com/en-us/azure/active-directory/users-groups-roles/domains-admin-takeover https://docs.microsoft.com/en-us/azure/active-directory/user... It's still not well supported for "external" takeover but it's disappointing that your support queue didn't point you to the docs on this. Per below though, if someone made it "managed" through DNS verification, yeah, that's hard. Keywords to search in this scenario "viral admin takeover AAD"