Reading Time: 3 minutes
Share:
Twitter
LinkedIn
Facebook
Reddit
Whatsapp
Follow by Email

Whilst doing some daily Azure Administration I came across an error on one of my App Services. The App service in question uses vNet Integration and the certificate for the virtual network had become out of sync. I am not 100% sure how this happened, but there was an issue with Azure the night before. Luckily it is easy to fix, just not as intuitive as you would hope. Below you will find a guide on how to get your certificate back in sync.

The Error

In the overview blade of an App Service, you will see an error like the one below.

If you click the warning you will come to this screen.

The fix

Unfortunately, you are unable to fix the issue here. Instead, navigate to the App service plan that is hosting the web app. The easiest way to do this is to close the current Virtual Network Integration blade. And then click on your App service plan in the Overview blade.

In the App Service Plan click on Network on the left-hand side under settings.

Now under VNET Integration click on Click here to manage

Now click on the VNET NAME that is having the issue. This can be found from the Virtual Network Integration blade from before.

Now click on Sync Network. You will also notice in this new blade you will get a list of Apps using the Virtual Network Integration.

You will now have a warning box popup. Read it, understand it and then click Yes

The synchronisation will now start. You can monitor it under the notification bell (top right).

After some time your certificates will be back into sync.

Note: If you have any failures just click Sync Network again.

I hope you found this article helpful. If you have any questions please reach out.

Share:
Twitter
LinkedIn
Facebook
Reddit
Whatsapp
Follow by Email

Pixel Robots.

I’m Richard Hooper aka Pixel Robots. I started this blog in 2016 for a couple reasons. The first reason was basically just a place for me to store my step by step guides, troubleshooting guides and just plain ideas about being a sysadmin. The second reason was to share what I have learned and found out with other people like me. Hopefully, you can find something useful on the site.

0 Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

*

I agree