<feed xmlns="http://www.w3.org/2005/Atom"><title>tls 1.1</title><id>https://evotec.xyz/es/tags/tls-11/index.atom.xml</id><updated>2019-12-14T11:01:16.0000000Z</updated><subtitle>Evotec Main Website</subtitle><link href="https://evotec.xyz/es/tags/tls-11" /><link href="https://evotec.xyz/es/tags/tls-11/index.atom.xml" rel="self" type="application/atom+xml" /><entry><title>Invoke-RestMethod : The underlying connection was closed: An unexpected error occurred on a send while connecting Graph API</title><id>https://evotec.xyz/es/blog/invoke-restmethod-the-underlying-connection-was-closed-an-unexpected-error-occurred-on-a-send-while-connecting-graph-api</id><link href="https://evotec.xyz/es/blog/invoke-restmethod-the-underlying-connection-was-closed-an-unexpected-error-occurred-on-a-send-while-connecting-graph-api" /><updated>2019-12-14T11:01:16.0000000Z</updated><summary>In the last few days, I’ve got two reports that my PowerShell module for Office 365 Health suddenly started giving errors. This was a bit weird because it worked perfectly fine on my end. But while I could understand one person having an issue of their own, with their network or firewalls, if the second person comes along with the same report, that means something else is going on.</summary><category term="invoke-restmethod" /><category term="office 365" /><category term="powershell" /><category term="tls 1.0" /><category term="tls 1.1" /><category term="tls 1.2" /></entry></feed>