What permissions should I have in my Microsoft Azure account to use the Site24x7 App for monitoring?
You can auto-discover and monitor all your Azure resources by authenticating with the Site24x7 App. The following permissions are required to monitor your Azure resources with the Site24x7 App:
- A Microsoft Azure account with Owner role for the Azure subscription that needs to be monitored.
- Access to the Active Directory tenant.
- Contributor/Reader role to the Site24x7 App.
Note: If you don't want Site24x7 to have access to a subscription, you can try the custom app method to start monitoring the Azure resources.
Refer our help documentation to learn more.
Related Articles
Azure VM Agent-level metrics not visible
Problem After integrating the Site24x7 server agent with Azure VMs, agent-level metrics are not visible in the Site24x7 dashboard. The agent fails to install the required monitoring extension on the Azure VM. Error message ...Sync Microsoft Entra ID users to Site24x7 via Zoho Directory
If you want to sync your user data from Microsoft Azure AD to Site24x7, you can do it with Zoho Directory's conditional assignment feature. Once synced, you can easily add users in Site24x7 without requiring manual intervention. The users added to ...Configure gMSA Permissions for Secure SQL Monitoring in Site24x7
The Site24x7 App Monitoring Agent can be configured to monitor a Microsoft SQL Server instance. During setup via the Agent Manager command-line interface, the agent's Windows service logon account must have the appropriate domain credentials to ...How many API calls does Site24x7 Azure monitor make
Site24x7 Azure monitoring uses APIs to retrieve the health and performance metrics, as well as the configuration data on your Azure resources. Microsoft charges based on the total number of API calls made. Therefore, the cost incurred is directly ...What should I do if Service Health data collection in Microsoft 365 monitor is not happening?
Your Microsoft 365 monitor's Service Health data collection may have stopped because of the recently updated Microsoft 365 Service Communications API policy. Follow the steps below if Service Health data collection in your Microsoft 365 monitor is ...