Closed vandreytrindade closed 4 years ago
Found the same to be true today:
reaching out to see if I can find out more.
It's working again!
@vandreytrindade can you confirm it's still working? I'm unable to reach the endpoints.
@mattmcnabb Hi! Yes, it is still working:
$Session = New-SCSession -Credential $Cred
$Session
UserName Cookie
vandrey@domain IFYftmE55qBafZGkJlN2wvwm2P6eKTs8AT2Q9....
Weird, I'm able to use it again today! Thanks for letting me know!
np! =]
@vandreytrindade Have you checked on this again? It appears to be working for me.
Here's a really strange notion - this same thing has happened every fall since I published this module! I'm guessing it has something to do with certificate expiration or DNS. Back in 2017 when it happened the first time someone from MS clued me in to a different hostname that worked temporarily for the API, and then it was fixed shortly thereafter.
@mattmcnabb Hi! I've just checked and it's really working again. Thanks for the heads-up.
PS C:> New-SCSession -Credential $Cred Invoke-RestMethod : The service is unavailable. No C:\Program Files\WindowsPowerShell\Modules\O365ServiceCommunications\1.5.12\functions\New-SCSession.ps1:60 caractere:22