I see that people have had fun in this thread.
I was not amused. The issue encountered today had nothing to do with today’s experiment. Instead we got hit for the 8th time in 11 months with a mysterious issue that Microsoft hasn’t been able to resolve so far. Hopefully the logs this time show them something new – at least the symptom and error was slightly different than before after the latest round of change recommended.
What we were able to do of the experiment did provide information.