Office 365 – DTD is prohibited in this document issue
Got trouble Connection PowerShell to SharePoint online? This could be the resolution to your troubles.
I had this myself, or we had it in our Company tenant. This is what the issue was and this is how I fixed it:
When trying to connect to PowerShell for SharePoint Online, using the Connect-SPOService command, we got a error that did not tell us anything.
The error is:
Connect-SPOService : For security reasons DTD is prohibited in this document. To enable DTD processing set DtdProcessing property on XmlReaderSettings to Parse and pass the settings into XmlReader.Create method.
Well, its almost a joke right…
When searching the web for information on this particular, I struck zero…all I could find related to the ISP and the default search provider something. I quickly dismissed them as unrelated.
Then after some time had passed, I found a similar issue, this seemed related and it was a connectivity issue same as mine (If I still had the link I would give credit to where credit is due). This fellow had resolved the issue by adding a missing DNS record.
This made me think, since our tenant has existed since way Before Office 365 existed (BPOS) perheps we were also missing some of the required DNS records?
I checked with my collegues, and apparently we were missing the record as well.
So, if you ever see or get the ‘DTD prohibited’ issue, remember to check the DNS for the following record:
Info: Used by Office 365 to direct authentication to the correct identity platform More Information
After I added this to DNS, Connect-SPOService works just fine!
|Microsoft’s official explaination on the DNS record:
What’s the purpose of the additional Office 365 CNAME record?
If Office 365 manages your domain’s DNS records,, Office 365 sets up this CNAME record for you.
If you are managing DNS records for your domain at your DNS host, to create this record, you create this record yourself by following the instructions for your DNS host.
References and Credits‘
Nope, not this time…Credits & many thanks to To all of you.