Microsoft: Azure PowerPack Release Notes, version 122

Version 122 of the "Microsoft: Azure" PowerPack updates the Execution Environment for Python 3.9 compatibility and adds new Dynamic Application coverage for Azure Virtual Desktop, Front Door, and Fabric Capacities resources. This release also addresses several customer-reported issues.

• Minimum Required Skylar One (SL1) Version: 12.3.0

Before You Install or Upgrade

Ensure that you are running version 12.3.0 or later of Skylar One before installing the "Microsoft: Azure" PowerPack.

For details on upgrading Skylar One, see the relevant Skylar One Platform Release Notes.

Before using the multiple subscription functionality, ScienceLogic recommends that you review your device capacity and load limits to determine the best method for implementation.

Installing the PowerPack

To install this PowerPack:

1. Search for and download the PowerPack from the PowerPacks page at the ScienceLogic Support Center (Skylar One > PowerPacks).

2. In Skylar One (formerly SL1), go to the PowerPacks page (System > Manage > PowerPacks).

3. Click the Actions menu and choose Import PowerPack. The Import PowerPack modal appears.

4. Click Browse and navigate to the PowerPack file from step 1.

5. Select the PowerPack file and click Import. The PowerPack Installer modal displays a list of the PowerPack contents.

6. Click Install. The PowerPack is added to the PowerPack Manager page.

See the manual Monitoring Microsoft Azure for instructions on using the new PowerPack.

Upgrading the PowerPack

By default, installing a new version of a PowerPack overwrites all content in 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 the new version of the PowerPack from overwriting local changes for some commonly customized fields.

To upgrade the "Microsoft: Azure" PowerPack from version 104 and later:

1. Familiarize yourself with the Known Issues for this release.
2. See the Before You Install or Upgrade section. If you have not done so already, upgrade your system to the minimum required platform version or later release.
3. Search for and download the PowerPack from the PowerPacks page at the ScienceLogic Support Center (Skylar One > PowerPacks).

4. Before importing and installing this version of the PowerPack, you must disable the existing tree of Azure parent and component devices, recursively. To do so:

• Go to the Device Components page (Devices > Device Components)
• Collapse the root Azure component device.
• Select the root Azure device's checkbox.
• Click the Select Action drop-down menu.
• Under Change Collection State, select Disabled (recursive), and then click [Go].

5. Go to the PowerPack Manager page (System > Manage > PowerPacks).
6. Click the Actions menu and select Import PowerPack.
7. Import the Version 122 of the "Microsoft: Azure" PowerPack. For more information on importing PowerPacks, see the section on Installing a PowerPack.
8. Click the Install button.
9. If you are implementing the multiple subscription feature, go to the Credential Management page (System > Manage > Credentials) and create a new credential or edit an existing one as needed for use with the multiple subscription configuration. (For more information, see the manual Monitoring Microsoft Azure.)
10. Enable the existing tree of Azure parent and component devices, recursively. To do so:

• Go to the Device Components page (Devices > Device Components)
• Collapse the root Azure component device.
• Select the root Azure component device's checkbox.
• Click the Select Action drop-down menu.
• Under Change Collection State, select Active (recursive), and then click [Go].

Features

This release includes the following features:

• Dynamic Applications that enable Skylar One to discover, model, and monitor performance metrics and collect configuration data for Azure resources
• Event policies that are triggered when Azure resources meet certain status criteria
• Device classes for each Azure data center location and all of the Azure resources that Skylar One monitors
• Example credentials for discovering Azure resources
• 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

Enhancements and Issues Addressed

The following enhancements and addressed issues are included in this release:

• Updated the execution environment to include the dependencies required for deployment on Skylar One v12.x (Python 3.6) and Skylar One v13.x (Python 3.9).

  If you are on a 13.x version of Skylar One, you must remove several libraries from the "Microsoft: Azure EE v122" execution environment's aligned libraries list before upgrading to version 122 of the "Microsoft: Azure" PowerPack. For more information, see the Before You Install or Upgrade section.

• Made the following updates to the "Microsoft: Azure Host Pool Performance" Dynamic Application:

  • Added the new collection objects "Host Pool Name," "Host Count," "Total Sessions," "Drained Host Count," and "Max Session Limit."

  • Added the new presentation objects "% Fill," "Drained Host Count," and "Total Sessions."

  • Added a new "Session Fill High" threshold.

  • Added four new alerts and event policies for host pool availability and session fill.

• Added a new "Microsoft: Azure Host Pool Scaling Configuration" Dynamic Application, which automatically aligns to the host pool device and triggers events when a scaling plan is disabled or unattached.

• Added two new Dynamic Applications, "Microsoft: Azure Fabric Capacity Discovery" and "Microsoft: Azure Fabric Capacity Configuration," for discovering and monitoring Azure Fabric capacities.

• Updated the "Microsoft: Azure CDN Service Discovery" and "Microsoft: Azure CDN Profile Discovery" Dynamic Applications to discover only Content Delivery Network (CDN)-type resources, now that separate Dynamic Applications discover Front Door resources.

• Added BGP Availability and ARP Availability metrics (Primary, Secondary, and Overall) to the "Microsoft: Azure ExpressRoute Circuit Performance" Dynamic Application. A Major alert triggers when availability drops below 100% for a single peer. A Critical alert triggers when both peers are down, automatically suppressing the Major alert.

• Added four new Dynamic Applications for monitoring Microsoft: Azure Front Door resources:

  • "Microsoft: Azure Front Door Discovery"

  • "Microsoft: Azure Front Door Configuration"

  • "Microsoft: Azure Front Door Performance"

  • "Microsoft: Azure Front Door Service Discovery"

• Updated the following network and firewall Dynamic Applications with new collection objects, alerts, and events:

  • "Microsoft: Azure Application Gateway Performance"

  • "Microsoft: Azure Virtual Network Gateway Performance"

  • "Microsoft: Azure ExpressRoute Circuit Performance"

  • "Microsoft: Azure Firewall Performance"

• Updated the "Microsoft: Azure Unified Alerts Performance" Dynamic Application to better align alerts to the Azure resource, service, or subscription component that generated them. In addition, added an "Enable Unified Alert Collection" threshold that lets you disable alert collection at the subscription level.

• Converted the Azure Performance Dynamic Applications to use Azure's getBatch API endpoint, reducing the overall number of API requests made by the PowerPack.

• Removed support for the deprecated Microsoft Cloud Deutschland sovereign cloud, including the "Azure Credential - Germany" sample credential; the "Azure Location Germany Central" and "Azure Location Germany Northeast" Device Classes; and the "Azure Location Germany AP" Content Object. In addition, updated the silo_arm library to version 120.1.7.

• Added support for filtering virtual machine discovery by tag, in addition to the existing power-state filtering.

• Updated all event policy descriptions in the PowerPack for consistency and to help Skylar AI use them more effectively. This text change did not impact event policy behavior.

  If you have previously modified the PowerPack's event policy descriptions, upgrading to this release might overwrite those modifications.

• Added "Microsoft Azure OpenAI" and "Microsoft Azure OpenAI Service" Device Classes along with the following Dynamic Applications to support monitoring Azure OpenAI resources:

  • "Microsoft: Azure OpenAI Discovery"

  • "Microsoft: Azure OpenAI Configuration"

  • "Microsoft: Azure OpenAI Performance"

  • "Microsoft: Azure OpenAI Service Discovery"

• Ensured the "Microsoft: Azure OpenAI Configuration" Dynamic Application displays all "Capabilities."

• Updated the "Microsoft: Azure Recovery Services Vault Configuration" Dynamic Application to Azure API version 2025-08-01.

• Addressed an issue in which cached data stored without an expiration date caused collector file systems to fill up. (Case: 00484390)

• Resolved an issue in which a typo in the "Availability" collection object caused the "Microsoft: Azure Event Grid Sys Topic Subscription Discovery" Dynamic Application to return no data. (Cases: 00607239, 00503208)

• Addressed an issue in which excessive HTTP 429 responses from Azure caused false-positive poller availability and flapping events. This update improves retry and exception handling, removes the availability component identifier, and adds a new alert. (Case: 00507231)

• Addressed an issue in which the "Microsoft: Azure Virtual Machine Configuration" Dynamic Application did not collect SKU details for the GermanyWestCentral region. (Case: 00492691)

• Updated the "Microsoft: Azure App Discovery" Dynamic Application to discover all Azure application types except for "functionapp" and "api." (Case: 00474436)

• Resolved an issue that prevented the discovery API URL from constructing correctly for the "Microsoft: Azure ExpressRoute Peering Discovery" and "Microsoft: Azure ExpressRoute Circuit Connection Discovery" Dynamic Applications. (Case: 00468949)

• Addressed an issue in which the Azure "Microsoft Azure: Vanish Terminated VMs" run book action failed with the error "'str' object has no attribute 'get'." (Case: 00442556)

• Updated the "Azure Virtual Machine A1 v2" device class to remove a double space in the device class name. (Case: 00711618) 

Known Issues

The following known issues affect version 122 of the "Microsoft: Azure" PowerPack:

• There is an issue with device groups in Skylar One that might affect the execution of run book actions. As a workaround, after installing the PowerPack, resave the Azure device groups:

  1. Go to the Device Groups page (Devices > Device Groups).

  2. Locate one of the Microsoft Azure device groups and click its edit icon ().

  3. Click Save.

• Microsoft does not have endpoints for Tenants (Active Directory) and CDN for China-based Azure subscriptions. If you have a China-based subscription, ScienceLogic recommends that you disable the collection objects in the "Microsoft: Azure Active Directory Tenant Discovery" and "Microsoft: Azure CDN Service Discovery" Dynamic Applications.

  1. To disable the collection objects, run the following SQL query to obtain the device IDs (DIDs) with the Dynamic Applications that need to be disabled:

     #Replace the <ROOT_ID1, ROOT_ID2,...> and run the query to get DIDs

     SELECT DISTINCT(did) FROM master.dynamic_app_collection AS app_coll

     JOIN master.dynamic_app AS app ON app.aid = app_coll.app_id

     WHERE

     did IN (SELECT did FROM collector_state.V_device WHERE parent_did IN (<ROOT_ID1, ROOT_ID2,...>)) AND

     app.app_guid IN ("1E854E85AC1734486E598711DD3C6E8B", "D7403B5542C9D6DBB5DD0BE247CDB084"); 

  2. Then, to disable the collection objects from the "Microsoft: Azure Active Directory Tenant Discovery" and "Microsoft: Azure CDN Service Discovery" Dynamic Applications, run the following query:

     #Replace <DID1, DID2,...> with data collected in Query 1

     UPDATE master.dynamic_app_collection AS app_coll

     JOIN master.dynamic_app AS app ON app.aid = app_coll.app_id

     SET

     app_coll.`collect` = 0,

     app_coll.edited_by = 1

     WHERE app.app_guid IN ("1E854E85AC1734486E598711DD3C6E8B", "D7403B5542C9D6DBB5DD0BE247CDB084")

     AND app_coll.did IN (<DID1, DID2,...>);

• Devices with special characters are not discovered. Therefore, any device that contains special characters displays as an empty service container under its Azure service. This will be addressed in an upcoming release.
• After upgrading, critical events might appear for SQL database resources at the Azure root component level. This is expected and should disappear after a few polling cycles. If this does not resolve, contact ScienceLogic Support.
• If you encounter a 529 (server overloaded) error, this is usually a temporary issue with the Microsoft API service.
• In some environments, the installation window might continue to show that the PowerPack is still installing even though installation has finished. If this occurs, you can close the window and check the PowerPack version number in the PowerPack Manager page (System > Manage > PowerPacks) to confirm that installation has completed.
• The "System Availability" metric requires an availability report every five minutes. However, the "Microsoft Azure: Virtual Machine Discovery" Dynamic Application runs every 15 minutes by default, which causes gaps in the data. To avoid seeing gaps in System Availability, reduce the default poll time for the Discovery Dynamic Application to five minutes.
• When discovering a large number of component devices, the discovery process can cause the appearance of numerous critical events with the message, "Large backlog of asynchronous jobs detected."
• The Dynamic Application "Microsoft: Azure Backup Policy Configuration" retrieves an additional parameter (HourlyLogBackup) that is not displayed in the Azure portal. The parameter does not contain a value. This issue is caused by a parameter being available in the Azure API but not in the Azure portal.
  

  This issue does not occur for Microsoft Azure Government subscribers.

• In Microsoft Azure, no count appears for Recovery Service Vault > Backup items > Azure Backup Server. This is an issue in the Azure API.
• The API for Microsoft Azure Government does not currently provide performance data for Azure Application Gateways. This is an issue in the Azure API.
• The API for Microsoft Azure Government does not currently support the following performance data for Azure SQL Databases: deadlock, dtu_consumption_percent, dtu_limit, dtu_used, log_write_percent, sessions_percent, storage, storage_percent, workers_percent, and xtp_storage_percent. This is an issue in the Azure API.