Azure EA API is getting deprecated and is already being replaced by EA BillingExport. If you have an Azure EA account, its deprecation means you should migrate it into EA Billing Export (using the Microsoft Cost Management) mechanism, as described in the following sections.
Azure notification:
Through our migration process, we seamlessly transition your existing configuration and historical data to the new account on Anodot. Despite this change, your account will remain visually and functionally identical. The only difference lies in our sourcing method for Azure data, now utilizing exports instead of the API. For the migration, you will need to create an application, storage account, container, and export in the Azure console.
Migration steps on Anodot
- From the Accounts > Cloud Accounts page you will see the relevant EA accounts requiring migration, indicated by the red Migrate button.
Note: once the migration is completed the EA account row will be removed and the new Export account row will be added. -
Click Migrate to start the migration.
Here are the steps you need to follow in Anodot and Azure console for the migration:
App Registration
- Go to the Azure console, navigate to App Registrations, and click New registration.
- Define a name for the application and click Register.
- For the account you created, make a note of the following values as you will need to enter them later on in the Anodot platform:
- Display Name
- Application (client) ID
- Directory (tenant) ID - From the left menu, navigate to the Certificates & secrets page, and click New Client Secret.
- Define a description, choose the expiration period (we recommend 730 days), and click Add.
- Make a note of the Secret Value, as you will need to enter it in the Anodot platform.
- In Anodot, enter the values you made a note of in the above steps and click Test.
Storage and billing export
The steps required for the billing export include creating a storage account, providing permissions, creating a container, and creating an export.
Create Storage Account
If you want to use an existing storage account, skip this step and go to the providing permissions step. Otherwise, perform the following steps:
- Navigate to the Storage account page, and click Create.
- Define the following for the storage account:
- Subscription: The subscription to which the storage account will be related to.
- Resource group: The resource group to which the storage account will be related to.
- Storage account name: The name of the storage account (make a note of this name, as you will
need to enter it in the Anodot platform).
- Region: The region to which the storage account will be related to.
Optional:
In case you want to restrict access to your storage account to Anodot's IP only follow the following steps:
- From the Storage Account page click on the Networking from the left menu.
- In the Public network access choose the "Enabled from selected virtual networks and IP addresses" option.
- In the Address range mention Anodot public IPs - reach to our support to receive those IPs (support@anodot.com).
Provide permissions to the application
- Navigate to the Storage Account page, and select the storage account you created in the previous step.
- Navigate to Access Control (IAM) and then click Add > Add role assignment.
- In the Role tab, search for the Storage Blob Data Reader role, choose it, and click Next.
Note: this role grants read-only access to Azure Storage blob containers and their data- this will allow Anodot to read your export data from the container. For more information review Azure documentation. - In the Members tab, click Select Members, search for the application name you created in the App Registration step, choose it, and click Review + assign.
- Navigate to the Subscription where the Storage Account is located (from the Subscriptions page).
- Navigate to Access Control (IAM) and then click Add > Add role assignment.
- In the Role tab, search for the Monitoring Reader role, choose it, and click Next.
Note: This role provides read-only access to monitoring data across various Azure resources. For more information review Azure documentation. - In the Members tab, click Select Members, search for the application name you created in the App Registration step, choose it, and click Review + assign.
Create Container
If you want to use an existing container, skip this step and go to the create export step. Otherwise, perform the following steps:
- Under the Storage account you created, navigate to the Containers page from the left menu and click Add Container.
- Set the Anonymous access level to Private (no anonymous access), and then click Create. Make a note of the container name, as you will need to enter it in the Anodot platform.
Create Export
- Navigate to the Cost Management + Billing page.
- From the left menu, navigate to the Exports page, and click Create.
Note: If your storage account is protected by a firewall, you can create an export using an SAS key. Contact Anodot support for more details and guidance. - Define the following for the export:
- Export type: "Daily export of month-to-date costs"
- Metric: "Cost and usage details (actual)
enter the required values ad displayed in the screenshot below, and click Create.
Note:
- After the migration you can onboard another new account with Amortized costs. Simply choose the Amortized value in the Metric.
- Make a note of all the values from the export configuration as you will need to enter them in the Anodot platform. - Navigate to the Exports page, mark the export you just created, and click Run now.
- In Anodot, enter the values you noted above and click Next.
If you navigate to the Cloud Accounts page in Anodot, you will see that the interface type has been changed to "EA_Export". We kept the account with all the historical data and configuration, and the next time Anodot gathers the updated data, it will come from the export you just created in Azure.