PRTG Manual: Microsoft Azure Subscription Cost Sensor

Permissions for the Azure custom role

• This sensor requires an Azure custom role with permissions for specific actions.

• Create an Azure custom role and add permissions for the following actions:

• • "Microsoft.Consumption/*/read",
  • "Microsoft.Consumption/*/action",
  • "Microsoft.CostManagement/query/read",
  • "Microsoft.Billing/*/read"

For more information, see the Knowledge Base: How do I obtain credentials and create custom roles for the Microsoft Azure sensors?

Credentials

• This sensor requires credentials for Microsoft Azure.

CSP subscriptions

• This sensor does not support cloud solution provider (CSP) subscriptions.

IPv6

• This sensor supports IPv6.

Performance impact

• This sensor has a very low performance impact.

Scanning interval

• The minimum scanning interval of this sensor is 1 minute.

• The recommended scanning interval of this sensor is 4 hours.

Knowledge Base

• Knowledge Base: How do I obtain credentials and create custom roles for the Microsoft Azure sensors?

Budgets

If additional channels for the budget usage in your Microsoft Azure subscription are enabled or disabled.

Cost Forecast

If the additional channel with a cost forecast for your Microsoft Azure subscription is enabled or disabled.

Most Expensive Service

Select if you want to show the most expensive service of your Microsoft Azure subscription in the sensor message:

• Disable (default)
• Enable

Most Expensive Service Category

This setting is only visible if you select Enable above.

Select the category for which you want to show the most expensive service in the sensor message:

• Resource group
• Resource type
• Resource ID
• Location
• Service name

Primary Channel

Select a channel from the list to define it as the primary channel. In the device tree, PRTG displays the last value of the primary channel below the sensor's name. The available options depend on what channels are available for this sensor.

You can set a different primary channel later by clicking below a channel gauge on the sensor's Overview tab.

Graph Type

Define how this sensor shows different channels:

• Show channels independently (default): Show a graph for each channel.
• Stack channels on top of each other: Stack channels on top of each other to create a multi-channel graph. This generates a graph that visualizes the different components of your total traffic.
  You cannot use this option in combination with manual Vertical Axis Scaling (available in the channel settings).

Stack Unit

This setting is only visible if you select Stack channels on top of each other above.

Select a unit from the list. PRTG stacks all channels with this unit on top of each other. By default, you cannot exclude single channels from stacking if they use the selected unit. However, there is an advanced procedure to do so.

Result Handling

Define what PRTG does with the sensor result:

• Discard result (default): Do not store the sensor result.

• Store result: Store the last sensor result in the \Logs\sensors subfolder of the PRTG data directory on the probe system. The file name is Result of Sensor [ID].log. This setting is for debugging purposes. PRTG overwrites this file with each scanning interval.

This option is not available when the sensor runs on the hosted probe of a PRTG Hosted Monitor instance.

In a cluster, PRTG stores the result in the PRTG data directory of the master node.

Current Period Cost

The current period cost

Downtime

In the channel table on the Overview tab, this channel never shows any values. PRTG uses this channel in graphs and reports to show the amount of time in which the sensor was in the Down status

Forecast

The cost forecast

[Budget] Used

The used budget

This channel is the primary channel by default.

[Budget] Used %

The used budget (%)

Previous Period Cost

The previous period cost