Introduction

The following sections provide an overview of Microsoft Azure and the Microsoft: Azure PowerPack:

What Does the Microsoft: Azure PowerPack Monitor?

To monitor Microsoft Azure resources using SL1, you must install the Microsoft: Azure PowerPack. This PowerPack enables you to discover, model, and collect data about Azure resources.

The Microsoft: Azure PowerPack includes:

Dynamic Applications to discover, model, and monitor performance metrics and/or collect configuration data for the following Azure resources:

Active Directory tenants
Archive storage

API Management
Application gateways
Application services
Azure API Apps
Azure Blob storage
Azure Cache for Redis
Azure Container Instances
Azure Container Registry
Azure Data Factory
Azure Database for MySQL
Azure Database for PostgreSQL
Azure Databricks
Azure Event Grid
Azure Firewall
Azure Functions
Azure Kubernetes Services (AKS)
Azure Service Buses (Relay)
Batch Accounts
Content Delivery Networks
Cosmos DB accounts
Data Science virtual machines
Disk storage
DNS zones
ExpressRoute circuits
ExpressRoute gateways
Function apps
Key Vaults
Load balancers
Managed storage disks
Network security groups
Queue storage
Recovery Services vaults
Resource groups
Site recovery configurations
Spot virtual machines
SQL databases
SQL managed instances
SQL servers
Storage accounts
Table storage
Traffic Manager profiles
Virtual machine scale sets
Virtual machines
Virtual network subnets
Virtual network gateways
Virtual networks
VPN gateways
Web apps
Web Application Firewalls (WAF)

Device Classes for each Azure data center location and all of the Azure resources SL1 monitors
Event Policies and corresponding alerts that are triggered when Azure resources meet certain status criteria
Example credentials you can use as templates to create SOAP/XML credentials to connect to Azure
A Credential Test to ensure that your Azure credential works as expected
Run Book Action and Automation policies that can automate certain Azure monitoring processes
Limited monitoring is available for services based on the Azure Resource List and Azure Resource Health APIs. The services are modeled as device components which can be used for CMDB syncing. Availability information is collected and used for alerts, and Azure alerts are collected and aligned to the related service. There is no performance monitoring, so all the device components created by the "AWS: Resource List Discovery" Dynamic Application are non-billable. The services included are:

Azure Analysis Services
Azure Arc
Azure Bastion
Azure Cognitive Services
Azure Data Lake Storage
Azure Database for MariaDB
Azure Database for MySQL Flexible Server
Azure Database for PostgreSQL Flexible Server
Azure Database Migration Service
Azure Dedicated Host
Azure Digital Twins
Azure Front Door
Azure IoT Hub
Azure Purview
Azure Service Fabric
Azure Spring Cloud
Azure Stream Analytics
Azure Synapse Analytics
Data Lake Analytics
Event Hubs
HDInsight
Log Analytics
Media Services
Microsoft Purview
Mobile Apps
Notification Hubs
Power BI Embedded

What are Azure Locations?

An Azure location is an individual data center located in a specific geographic locale. The Dynamic Applications in the Microsoft: Azure PowerPack create a "location" component device for each discovered data center location.

The PowerPack supports the following Azure data center locations:

Australia Central (Canberra)

Australia Central 2 (Canberra)
Australia East (New South Wales)
Australia Southeast (Victoria)
Brazil South (Sao Paulo)
Canada Central (Toronto)
Canada East (Quebec)
Central India (Pune)
Central US (Iowa)
China East (Shanghai)
China East 2 (Shanghai)
China North (Beijing)
China North 2 (Beijing)
East Asia (Hong Kong)
East US (Virginia)
East US 2 (Virginia)
France Central (Paris)
France South (Marseille)
Germany Central (Frankfurt)
Germany North
Germany Northeast (Magdeburg)
Germany West Central
Japan East (Saitama)
Japan West (Osaka)
Korea Central (Seoul)
Korea South (Busan)
North Central US (Illinois)
North Europe (Ireland)
South Central US (Texas)
South India (Chennai)
Southeast Asia (Singapore)
US DoD Central (for Microsoft Azure Government only)
US DoD East (for Microsoft Azure Government only)
US Gov Arizona (for Microsoft Azure Government only)
US Gov Iowa (for Microsoft Azure Government only)
US Gov Texas (for Microsoft Azure Government only)
US Gov Virginia (for Microsoft Azure Government only)
UK South (London)
UK West (Cardiff)
West Central US
West Europe (Netherlands)
West India (Mumbai)
West US (California)
West US 2

Installing the Microsoft: Azure PowerPack

Before completing the steps in this section, you must import and install the latest version of the Microsoft: Azure PowerPack.

The following instructions describe how to install the Microsoft: Azure PowerPack for the first time. If you are upgrading to the latest version from a previous version, see the Microsoft: Azure PowerPack Release Notes for specific upgrade instructions.

By default, installing a new version of a PowerPack overwrites all content from a previous version of that PowerPack that has already been installed on the target system. You can use the Enable Selective PowerPack Field Protection setting in the Behavior Settings page (System > Settings > Behavior) to prevent new PowerPacks from overwriting local changes for some commonly customized fields. (For more information, see the section on Global Settings.)

The minimum required MySQL version is 5.6.0.

To download and install the PowerPack:

Search for and download the PowerPack from the PowerPacks page (Product Downloads > PowerPacks & SyncPacks) at the ScienceLogic Support Site.
In SL1, go to the PowerPacks page (System > Manage > PowerPacks).
Click the Actions button and choose Import PowerPack. The Import PowerPack dialog box appears.
Click [Browse] and navigate to the PowerPack file from step 1.
Select the PowerPack file and click Import. The PowerPack Installer modal displays a list of the PowerPack contents.
Click Install. The PowerPack is added to the PowerPacks page.

If you exit the PowerPack Installer modal without installing the imported PowerPack, the imported PowerPack will not appear in the PowerPacks page. However, the imported PowerPack will appear in the Imported PowerPacks modal. This page appears when you click the Actions menu and select Install PowerPack.