Open sympmarc opened 4 years ago
If we can't change the behavior of Connect-PnPOnline querying for msoid... can we trap the error better and give the user feedback that it's a DNS error? It probably took Marc and I an hour to get to the bottom of this the first time he encountered it. I would imagine casual users of the PnP don't have the patience to spend that much time troubleshooting.
Reporting an Issue or Missing Feature
My ISP is Cox, and they have one of those annoying custom error pages when there is a DNS error. When I use
Connect-PnPOnline
with-Credentials
, I get a DTD error because of the custom error page. I blogged about this here. The error is thrown because the cmdlet tries to openmsoid.tenantname.com
.The error looks something like this:
Because of this, I've been using
-UseWebLogin
. This causes other issues, but it generally gets the job done. Today I switched my DNS provider to Cloudflare which lets me use-Credentials
again, so I'm happy.The question is whether
Connect-PnPOnline
should be trying to hit themsoid.tenantname.com
at all. At least one Microsoft article saysmsoid
is obsolete and shouldn't be used. It's a "bug" in the sense that a crappy DNS provider can block connections. I'm not sure if there's an answer here, but it seemed worth reporting.Which version of the PnP-PowerShell Cmdlets are you using?
What is the version of the Cmdlet module you are running?
3.23.2007.1
How did you install the PnP-PowerShell Cmdlets?
@ToddKlindt @erwinvanhunen