A couple days ago I used Mr. Eric Shanks’ awesome script to setup and provide the needed data for my Azure setup in VMware vRealize Automation. One thing I found out today was that it created a Key that was only good for a day. It took me about 5 minutes to figure out why it was failing and then another 15-20 to fix it, so hopefully, this will save some people some time if they run into this error in vRO.

Now – The fix.

  • Go create another Key:

Login to Azure and in the left sidebar, click the “Blue Boat Anchor”, also labeled ‘Azure Active Directory’. Click App registrations and then click the App you created for vRA.

Now click ‘Keys’ and create a new key – Give it a description and an end date and the key, or “secret” will be provided to you. SAVE THAT NOW as it will not be displayed again. As you can see below I have already created a new key and you can see my expired key.

You are all set in the Azure Portal. Now to vRA.

  • Update the Azure Endpoint in vRealize Automation:

Login to vRA (assuming you are a Tenant, Fabric Admin, and IaaS Admin) and click ‘Administration, then ‘vRO Configuration’ then ‘Endpoints’.

Select the Azure endpoint that you would like to modify and go to the details tab. Paste your ‘Key’, or as VMware refers to is as your ‘Client Secret’, and click Finish.

 

If it was successful it will bring you back to the Endpoints screen, else it will say to check the logs. The logs are going to tell you it is an auth issue so I’d recommend verifying the string you are pasting is correct, else creating another Key and attempting this process again as you may have cut some of the Key off in the copy/paste operation.