Overview
Azure resources fail to associate with a Business Application for a small set of well-understood reasons: usually a permissions gap on the service principal or a mismatch in tag configuration. This article covers the most common causes and how to resolve them. Resources must be associated with a Business Application before they can be monitored, managed through automated tasks, or displayed on dashboards.
Business value
Correct resource association is the prerequisite for all downstream features in Business Applications. Resolving association failures ensures complete monitoring coverage and prevents gaps in visibility across your Azure estate.
How it works
Resources are associated with a Business Application either manually through the Resources tab or automatically through the automated resource association feature, which uses tag-based matching to discover and associate resources at runtime. Both paths require the service principal to have sufficient access to the target subscription and resource group.
When association fails, the resource either does not appear in Turbo360 at all, or it appears but is not linked to the expected Business Application.
Troubleshooting
-
Resource does not appear in the Add resources list
Cause: The service principal used by Turbo360 does not have Reader access to the subscription or resource group where the resource resides.
Fix: In the Azure portal, assign the Reader role to the Turbo360 service principal at the subscription or resource group scope. Allow a few minutes for the permission to propagate, then refresh the resource list in Turbo360. -
Automated resource association is not discovering resources
Cause: The tag key or tag value configured in the automated association rule does not match the tags applied to the Azure resources.
Fix: Navigate to Business Application > Automated map resources > Configure and verify the tag key and value. Compare these against the resource tags in the Azure portal. Correct any case or spelling discrepancies, then re-run the association. -
Resource appears in the list but cannot be saved to the Business Application
Cause: The resource type is not in the list of supported Azure resource types for Business Applications.
Fix: Check the Supported Azure resources article to confirm the resource type is supported. If the resource type is not listed, it cannot be associated at this time. -
Resource was associated but no longer appears in the Business Application
Cause: The resource was deleted or moved to a different subscription or resource group in Azure, or the service principal no longer has access to it.
Fix: Verify the resource still exists in Azure and has not been moved. Confirm the service principal retains Reader access to the current resource location. If the resource was moved, remove the stale association and re-add the resource from its new location. -
Automated association runs but associates resources to the wrong Business Application
Cause: Multiple Business Applications have overlapping tag rules that match the same resources.
Fix: Navigate to Business Application > Automated map resources > Configure across all Business Applications and review the tag rules for conflicts. Make tag values more specific, or restrict the association scope to a particular resource group, to avoid overlapping matches.