Applications Systems

Use a PowerShell Script to Create or Extract Credentials for Azure Cloud Infrastructure Monitoring

Before monitoring Microsoft Azure VMs in the Orion Web Console with the Cloud Infrastructure Monitoring feature, Azure must be configured to interact with the Orion Platform. The cloud account requires sufficient Azure AD and subscription permissions to add an AD app in the Azure Portal so the Orion Platform can retrieve status and metrics for Azure VMs. This article provides a script that uses Azure PowerShell cmdlets to automate the integration of the Orion Platform with Azure.

First published date

10/23/2018 8:00 PM

Last published date

9/24/2021 3:20 AM

Overview

To monitor Microsoft Azure VMs with the Orion Platform's Cloud Infrastructure Monitoring feature , Azure must be configured to interact with the Orion Platform. The cloud account requires sufficient Azure Active Directory (AD) and subscription permissions to add an AD app in the Azure Portal so the Orion Platform can retrieve status and metrics for Azure VMs. Identify and Access Management (IAM) permissions must also be configured. The Orion Platform also requires the Azure account credentials. 

The Configure Microsoft Azure for cloud monitoring in the Orion Platform article describes how to integrate Azure with the Orion Platform. You can also use the Get-AzureSamCreds.ps1 script to leverage Azure PowerShell cmdlets downloaded from the Microsoft Azure Downloads page (© 2018 Microsoft, available at https://azure.microsoft.com/en-us, obtained on October 23, 2018) to automate the integration. When executed, the script requests the Username and Password for the default Azure subscription and then integrates the Orion Platform with Azure.

Before using this script, note these details:

  • The script is designed for use with a single Azure subscription and a single tenant. It creates an AD app and links it to the subscription with a Reader role (© 2018 Microsoft, available at https://azure.microsoft.com/en-us, obtained on October 23, 2018). 
  • If you need to run the script again, be sure to remove any remnants left behind after running the script the first time. 
Disclaimer: The scripts are not supported under any SolarWinds support program or service. The scripts are provided AS IS without warranty of any kind. SolarWinds further disclaims all warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The risk arising out of the use or performance of the scripts and documentation stays with you. In no event shall SolarWinds or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the scripts or documentation.

 

 

Product section

Server Application Monitor

Cause

-

Resolution

To install the Azure PowerShell cmdlets used in the script:

  1. Navigate to the Microsoft Azure Downloads page (© 2018 Microsoft, available at https://azure.microsoft.com/en-us, obtained on October 23, 2018).
  2. Under Command Line Tools, click Windows Azure PowerShell.
  3. When prompted to run or save the .exe file, choose the Run button.
  4. Follow the online instructions to complete the installation.

After you install Azure PowerShell cmdlets, run the Get-AzureSamCreds.ps1 script at the command line to request the Azure credentials required to integrate with the Orion Platform.

    As you work with Azure accounts in the Orion Web Console, you'll be prompted to provide various Azure credentials. See Find Microsoft Azure account credentials for reference.

    Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.