And so it begins …
The day had only just begun … I got into the office … I grabbed a coffee … sat down at my desk.
I tried connecting to one of my Azure dev VM’s but for some reason I couldn’t RDP to it. I waited a bit of time and then tried again, but still no luck.
My Azure AutomationAccount was configured to automatically start and shutdown my VM’s each working day.
I checked the logs for my AutomationAccount and found the message
“The Server encountered an internal error. Please retry the request.”.
Previously, when it came to creating your own Microsoft bots, it required a certain degree of knowledge and custom development to make things actually happen.
This has all changed with the
Microsoft’s Cognitive Services portfolio. You can now have a bot up and running in 10 minutes – literally!
Have you published a long running web job in Azure and noticed that it has terminated with an ‘
Aborted’ status. Chances are that the job has timed out.
In this post I’ll explain what’s happening here and how you can fix this.
Azure offers the ability to set static IP addresses for hosted virtual machines. I recently had to configure this for some of our existing “classic” Azure virtual machines. The process is as follows.
Traditionally when setting up SSL for an IIS website, you could generate a CSR using IIS to provide to your relevant certificate authority.
If setting up a website using the
Azure App Service, the approach is slightly different. There’s a myriad of ways of can do this, however this is the easiest approach I’ve found.
One of the most common Azure administration tasks is scheduling an auto stop & start of your Azure VM’s to save you a few $$$.
Here’s a quick post showing how you can do this.
Azure now provides the ability to auto start and shutdown UPDATE: ARM based VM’s. If you are however still using a Classic VM, you can follow the below guide.