NetBackup IT Analytics Data Collector Installation Guide for the Cloud
- Pre-Installation Setup for Amazon Web Services (AWS)
- Pre-Installation setup for Amazon Web services (AWS)
- Prerequisites for adding Data Collectors (Amazon Web services)
- Prerequisite Amazon Web services (AWS) configurations
- Configure an S3 bucket to receive billing reports
- Select cost allocation tags
- Create an AWS IAM user
- Mandatory probe user privileges
- Link AWS accounts for Collection of consolidated billing data
- Installation overview (Amazon Web Services - AWS)
- Add an Amazon Web Services (AWS) policy
- Pre-installation setup for Google Cloud Platform
- Pre-Installation Setup for OpenStack Ceilometer
- Pre-Installation Setup for OpenStack Swift
- Pre-Installation Setup for Microsoft Azure
- Pre-Installation setup for Microsoft Azure
- Setting up credentials for Microsoft Azure Data Collection
- Install the Azure PowerShell client on a Windows computer
- Find your tenant and subscription ID
- Register a new application for the Data Collector
- Create a principal and assign role to the application
- Prerequisites for Adding Data Collectors (Microsoft Azure)
- Installation overview (Microsoft Azure)
- Add a Microsoft Azure Data Collector policy
- Installing the Data Collector Software
- Validating Data Collection
- Uninstalling the Data Collector
- Manually Starting the Data Collector
- Appendix A. Firewall Configuration: Default Ports
Create a principal and assign role to the application
This step enables the newly registered application to have access rights to the subscription.
To enable access rights to the subscription, you can either create a Contributor role or create a combination of Reader and Custom roles for the application. Since Reader and Custom roles have restricted permissions compared to the Contributor role, you can choose to assign them to the application if the privileges available through the Contributor role do not comply with your organizational policy.
To create a principal and assign a Contributor role:
Create a Principal for the Application:
New-AzureRmADServicePrincipal -ApplicationId <APPLICATIONID>
Create a Contributor role:
New-AzureRmRoleAssignment -RoleDefinitionName Contributor -ServicePrincipalName <APPLICATIONID>
To create a principal and assign Reader and Custom roles:
Create a Principal for the Application:
New-AzureRmADServicePrincipal -ApplicationId <APPLICATIONID>
Create a Reader role:
New-AzureRmRoleAssignment -RoleDefinitionName Reader -ServicePrincipalName <APPLICATIONID>
Assign a Reader role to the application:
New-AzureRmRoleAssignment -RoleDefinitionName Reader -ServicePrincipalName <APPLICATIONID>
Create a custom role with JSON template.
For example, create a file
customrole.jsonusing the following:{ "Name": "<Role-Name>", "Id": null, "IsCustom": true, "Description": "<Role Description>", "Actions": [ "Microsoft.Storage/storageAccounts/listkeys/action" ], "NotActions": [], "DataActions": [], "NotDataActions": [], "AssignableScopes": [ "/subscriptions/<Subscription ID>" ] }Create a Custom role:
New-AzRoleDefinition -InputFile "C:\CustomRoles\customrole.json"
Assign a custom role to application:
New-AzureRmRoleAssignment -RoleDefinitionName <customeRoleName> -ServicePrincipalName <APPLICATIONID>