User Cost Attribution Migrate to Heartbeat-based Data
Due to the imminent deprecation of the Azure Consumption Usage Details API, Nerdio Manager’s User Cost Attribution feature is moving to a Log Analytic-based approach to log and report VM usage.
To support this change, customers are required to make some changes to their environment to ensure that the data reported is accurate.
Required Changes
The changes to the Subscription permissions detailed below can be made automatically from the banner message on the User Cost Attribution page, or directly from the target Subscriptions. See Add the Subscription Permissions Manually below for details. An account with Subscription Owner permissions must be used if the automatic approach is taken.
The changes to the User Cost Attribution WebApp must be made manually. See Add the App Service Setting to User Cost Attribution below for details.
Notes:
Performing the subscription changes manually results in the banner remaining within Nerdio Manager. Log in to Nerdio Manager as a Subscription Owner and re-save your User Cost Attribution configuration settings to resolve this issue.
Automatic Subscription changes are performed on a per-report basis. If multiple reports are in place for multiple subscriptions, please select the reports individually and select ‘update configuration’ for each report that references a different subscription.
The required changes are:
The permissions shown below must be granted to the User Cost Attribution Service Principal on the target Subscription.
Monitoring Reader
The App Service setting Is_Using_Heartbeat_Fetching must be manually added to your User Cost Attribution WebApp, and the value must be True.
Add the Subscription Permissions Manually
Note: This process must be repeated for each subscription that is used in the User Cost Attribution reports.
In the Azure portal, navigate to your target Subscription where the User Cost Attribution data resides.
Select Access control (IAM).
Add a role assignment.
Select Monitoring Reader as the role.
Specify your User Cost Attribution service principal.
Note: This is generally named NMW-CCL-APP-[Random String]
Optionally, the role can be validated from the Check Access function under Access control (IAM) for the subscription. Simply select Check Access and then specify the name of the service principal. The additional roles shown below are pre-existing.
Add the App Service Setting to User Cost Attribution
Note: This change should not be made until the Monitoring Reader role has been added for all in-scope subscriptions.
In the Azure portal, navigate to your User Cost Attribution WebApp.
Note: This is generally prefixed with NMW-CCL-APP.
In the Settings blade, select Environmental variables.
Select + Add, and enter the following details:
Name: Is_Using_Heartbeat_Fetching
Value: True
Save and apply the change.
Once all the above is complete, restart the User Cost Attribution WebApp.
Additional Information
Details on the depreciation of the Azure Consumption Usage Details API can be found here:
Comments (0 comments)