Slackbot
01/24/2024, 7:53 AMNick Pylarinos
01/24/2024, 7:55 AMMarco Hofmann
01/24/2024, 7:56 AMNick Pylarinos
01/24/2024, 7:56 AMMarco Hofmann
01/24/2024, 7:58 AMNick Pylarinos
01/24/2024, 7:59 AMNick Pylarinos
01/24/2024, 8:01 AMMarco Hofmann
01/24/2024, 9:54 AMMarco Hofmann
01/24/2024, 9:54 AMMarco Hofmann
01/24/2024, 11:08 AMMarco Hofmann
01/24/2024, 12:27 PMMarco Hofmann
01/24/2024, 12:28 PMMarco Hofmann
01/24/2024, 12:28 PMMarco Hofmann
01/24/2024, 12:28 PMc4rm0
01/24/2024, 12:29 PMThorsten
01/24/2024, 3:32 PMMarco Hofmann
01/24/2024, 3:34 PMRay Davis
01/25/2024, 2:51 PMMarco Hofmann
01/26/2024, 6:05 AMMarco Hofmann
01/26/2024, 6:05 AMAnd as we saw yesterday the users were contacting Azure West for the time period of the failures and Azure North when the issue had resolved itself. My current theory is that Microsoft is making a change in the Azure West region and causing an issue for specific customers.
Also as I mentioned we had another customer report the same issue as you yesterday for the same period and their environment seems to have a lot in common with yours. They also are not using Cloud connectors, Rendezvous protocol, Azure AD, and Azure non-domain VDAs. To my knowledge there are not a lot of customers with this specific config, which would be why the issue is not more widespread.
Would you be able to contact Microsoft and get their input on this issue, hopefully their logs will be able to shed more light on the cause of the issue.
Marco Hofmann
01/26/2024, 6:06 AMOwen Reynolds
02/02/2024, 5:16 PM