Azure
Connect
An Azure Lighthouse template deployed from the Azure portal.
Azure connects one subscription at a time through Azure Lighthouse. Choose Deploy on Azure in Polylane, then open the Azure portal, select the subscription and create the deployment. You need the Owner role on the subscription. The template delegates the subscription to a Polylane service principal that exists for this connection only, so Azure keeps each connection separate. It gives that principal Reader, Monitoring Contributor when you allow alert rules, and the role that lets Polylane remove its own delegation. It also creates a polylane-events resource group with an Event Grid topic and an event subscription for this connection that sends resource changes to Polylane. When you allow alert rules, Polylane adds an action group whose name starts with polylane-alerts- and metric alert rules for your production resources to that resource group, and investigates the alerts they send. Add that action group to your own rules to have Polylane investigate them too. Polylane stores no Azure credential. When you disconnect, Polylane removes its alert objects, its delegation and the identity of the connection. Then delete the event subscription of the connection, and the polylane-events resource group when no other Polylane connection uses the subscription.
Disconnect
Disconnecting stops every sync and check and deletes the credentials Polylane held. Polylane removes what Azure's API lets it remove. The following stays until you remove it yourself:
- Azure Lighthouse delegation (Service providers)
- polylane-events resource group
polylane cloud disconnect <id>Tools
3Operations agents can perform in threads.
Supported resources
73Resource types that show up in your infrastructure graph.