[azure_billing] Add documentation for assigning roles in department and billing account scopes.

[zmoog]

Proposed commit message

Add step-by-step instructions about which role to assign to the app registration to use the department or the billing account scopes.

When users want to collect billing metrics using the billing account scope, they must assign the "Department Reader" or the "Billing account reader" role in the IAM section at Cost Management + Billing. Before this change, we were only covering the subscription scope.

The department and billing account scopes allows users to access to data from multiple subscriptions.

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.

[muthu-mps]

@zmoog - As the requirement section already has a mention about the BillingReader role which can be assigned to subscription, department, or billing account. Can we update or remove the role definition here?

The App Registration requires the Billing Reader role to access the billing information for the subscription, department, or billing account.

[muthu-mps]

• Correct me if I am wrong, If the EA account holder is trying to access the billing metrics using the Department Id scope. Do they need to have the DepartmentReader role?
• We may need to update the document by adding account level scopes (EA, MCA) with roles permissions.

[zmoog]

Can we update or remove the role definition here?

Thanks, I missed that.

Correct me if I am wrong, If the EA account holder is trying to access the billing metrics using the Department Id scope. Do they need to have the DepartmentReader role?

You're right, we are not providing guidance for the department scope.

Unfortunately, I don't have the required access level to test this on our EA account. We need to find someone to help us here to cover the department scope.

[zmoog]

@muthu-mps, I still can't personally test this scenario, but I used the link you shared to update the docs.

[alaudazzi]

I left a few editing suggestions, otherwise LGTM.

[alaudazzi]

Suggested change

	1. In the [Azure Portal](https://portal.azure.com/), search for and select **Cost Management + Billing**.
	1. In the [Azure Portal](https://portal.azure.com/), search for and select **Cost Management** and **Billing**.

[zmoog]

@alaudazzi, I know it looks weird, but "Cost Management + Billing" is the actual name of the service:

Should we use "Cost Management and Billing" instead?

[alaudazzi]

Suggested change

	1. In the [Azure Portal](https://portal.azure.com/), search for and select **Cost Management + Billing**.
	1. In the [Azure Portal](https://portal.azure.com/), search for and select **Cost Management** and **Billing**.

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 56b2c01

History

• 💔 Build #9207 failed 4626b2e
• 💚 Build #9038 succeeded 12d2e6d
• 💚 Build #8949 succeeded f71e079
• 💚 Build #8803 succeeded 55ca443
• 💚 Build #8802 succeeded 7a82b03

cc @zmoog

[elastic-sonarqube]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

[elasticmachine]

Package azure_billing - 1.4.1 containing this change is available at https://epr.elastic.co/search?package=azure_billing