No tenant connected
- Connection ID
- —
- Azure tenant
- —
- Created
- —
- Accessible subscriptions
- —
Checking your TurtleNet session.
Connect your Azure tenants, map subscriptions, inspect relationships, and turn a changing estate into a topology you can work with.
Keep tenant connections organized without conflating TurtleNet account identity with Azure identity.
Alpha note: connection metadata is remembered in this browser for UX validation. Credentials and tokens remain server-side and are never stored in this library.
Your topology workspace is the source; exports and saved views become reusable architecture artifacts.
Build a topology to create the first diagram artifact.
Named diagrams, historical comparisons, and refreshable architecture views will live here without disrupting the main topology workspace.
Product identity, trial access, and Azure connection identity remain separate.
Trial state loading.
Alpha entitlement state is a UX contract only; production billing and server-side enforcement remain separate implementation work.
Short operational guidance without leaving the topology workspace.
Use the tenant library to authorize a separate Azure connection. TurtleNet account identity and Azure tenant identity stay distinct.
Select a subscription and run discovery. The alpha builds a diagnostic partial baseline and maps relationships into the canonical graph.
Select any resource on the map to inspect type, placement, relationship confidence, and canonical resource evidence.
Expired trials remain viewable. Topology refresh and diagram export are gated until subscription access is restored.