CUSTOM SOFTWARE · YOUR ENVIRONMENT

Your cloud,
documented like
a living system.

A customer-owned application for your Azure estate, system maps, and architecture knowledge. Built around your sources, your team, and the way you work.

Explore the example Design your application ↗

Customer-owned Your infrastructure Yours to evolve

01 / THE CONNECTED ESTATEBuilt around your world.

THE CONNECTED ESTATE

See the bigger picture.
Follow every connection.

From a single resource to the system around it. Explore how infrastructure, knowledge, and engineering work come together.

Meridian/Connected estate

FICTIONAL ESTATE

Connecting the estate…Preparing your 3D example

A SYSTEM OF SYSTEMS

Everything.
In context.

Your infrastructure. Your knowledge.
One connected view.

300RECORDS

7COLLECTIONS

630CONNECTIONS

300 records in view

Interactive example · Fictional Meridian estate

300 example records. No live sources connected.

Your sources/Your workflows/Your environment/Your application

The product

See the estate.
Understand the system.

Explore the interaction behind the application. This sanitized example shows how systems, infrastructure, and source evidence come together.

Production application platform

● Interactive example using sample data. Live Azure integration patterns inform the delivery; documentation automation, AI tools, and additional connectors are agreed and validated within each customer engagement.

How it stays current

Documentation
that doesn't rot.

Keep observed infrastructure facts separate from engineering judgment. The application brings collection, review, and accepted documentation into one workflow.

INTEGRATION FOUNDATION

OBSERVED FACTS

Collect the agreed facts.

Build scheduled collection around approved sources and read-only access. Show when each source was observed and where collection needs attention.

WORKFLOW PREVIEW

JUDGMENT · ENGINEER-APPROVED

Recurring problems become proposals.

The preview shows a proposed documentation diff with sources and an engineer’s decision. Connected ticket processing and durable approvals are implementation deliverables.

CUSTOM EXTENSION

CHANGE AWARENESS

Unexplained changes get flagged.

Compare observations and connect changes to approved tickets where evidence supports the link. Unmatched changes can enter a review queue.

Observed facts carry source context. Engineering judgment carries a review decision.

The ticket loop

Tickets in. Solutions, plans,
and records out.

A workflow we can build around your service desk: connect approved tickets to system context, prepare a proposed solution, and carry the engineer’s accepted decision into the record.

SolutionPilot

CORRELATERECOGNIZEDRAFTDOCUMENT

Azure DevOps / Identity & accessFICTIONAL TICKET · ADO-4483

Proposed solutionEXAMPLE DECISION

Current handling is a manual key rotation.+ Move supported consumers to identity-based access;+ retain a reviewed rotation plan for remaining keys.

Implementation planDRAFT FOR REVIEW

01Enable managed identity on the consuming workload02Move consumers off the shared key, one per change window03Disable shared-key auth · verify · document

Living record updatedEXAMPLE RECORD

JUDGMENTStorage access runbook — accepted identity decision, affected workloads, and source references added.

Azure DevOps read integrations provide a starting point. Ticket correlation and document updates are scoped and verified for each implementation. Additional connectors are roadmap options. Product names and logos belong to their respective owners.

Optional AI integration

Your estate,
connected to your AI.

Extend your application with a scoped context interface for an approved AI client. We agree the sources, access rules, provider, and evidence requirements as part of your implementation.

The living estate graphAzure · Microsoft 365 · Azure DevOps · GitHub

PROPOSED MCP INTERFACEREAD-ONLYSCOPE-GOVERNEDAUDIT REQUIREMENTSCUSTOMER-SCOPED INTEGRATION

Azure AI FoundryAgents grounded in live estate context

Claude Desktop · CodeOps questions, evidenced answers

Microsoft Copilot StudioInternal copilots that know your cloud

Your applicationsAny MCP-capable client or agent

YOUR MODEL, YOUR KEYSAZURE AI FOUNDRYANTHROPIC CLAUDEOPENAIIDENTITY AGREED PER DEPLOYMENT

Choose a provider that fits your hosting and data requirements. Authentication, credential storage, model access, and data destinations are defined and validated for your deployment.

Sources

Connect the sources
your team depends on.

Start with the sources that matter to your systems. Extend the application with agreed integrations for infrastructure, identity, delivery, and code.

INTEGRATION FOUNDATION

Azure

Resource Graph, ARM, cost, identity, and network state — the deployed truth.

RESOURCE GRAPHARMCOSTENTRA

INTEGRATION FOUNDATION

Microsoft 365

Licensing, security-plan coverage, and tenant signals for the estate view.

LICENSINGDEFENDER PLANS

INTEGRATION FOUNDATION

Azure DevOps

Delivery signals — projects, pipelines, and work-item flow beside the infrastructure they change.

PROJECTSWORK ITEMS

CONNECTOR ROADMAP

GitHub

Repositories, IaC, and deployment workflows joined to the running estate.

REPOSIACACTIONS

Optional AI integration

Ask your estate.
Get evidenced answers.

A preview of how a cited answer can connect system context, dependencies, and recorded changes. Live AI integration is tailored to your approved provider and evidence sources.

Your AI clientscripted preview · sample evidence

What does the payments system depend on — and did anything change this week?

EXAMPLE EVIDENCE SOURCES

aks user pool

postgres-prod

redis-cache

private endpoints

change feed

payments-platform runs on the private Kubernetes user pool and depends on postgres-prod (Private Link) and redis-cache. One material change this week: a new private endpoint was added Tuesday 14:32 — captured with evidence and pending owner review.

SYSTEMS MAPNETWORK TOPOLOGYCHANGE LOG · TUE 14:32

POTENTIAL CLIENT INTEGRATIONSAzure AI FoundryClaudeMicrosoft CopilotApproved MCP client

Enterprise posture

Your environment
stays under your control.

Start with a customer-hosted application and approved read-only sources. Define the access, identity, review, and audit requirements together.

DEPLOYMENT MODEL

Built for your environment. Handed over to your team.

We tailor the application to your estate and deploy it in your Azure environment, or the hosting you choose. You receive the source, deployment assets, and operating documentation. Your application can evolve independently, with support and further development scoped separately.

YOUR HOSTINGCUSTOMER-OWNED SOURCEAGREED DATA BOUNDARIESYOURS TO EXTEND

Review the pilot model ↓

CUSTOMER IMPLEMENTATION DESIGN

01Approved sourcesAzure · repositories · owner input

READ-ONLY

SolutionPilotDedicated application identityPRIVATE

APPROVAL

03Controlled outputsWeb · wiki · document · review queue

Least privilegeServer-side secretsEvidence provenanceAudit trail

A focused first engagement

Start with one
private pilot.

Prove the workflow on a contained scope, agree success criteria before access, and leave with a working application plus an approved architecture baseline.

01One agreed Azure scopeCustomer-controlled, read-only access

02One or two priority systemsSelected for operational value

03Two initial documentation viewsAligned to your team and standards

04Source code and operating handoverAcceptance criteria agreed up front

Design the pilot ↗

No tenant access is needed for the first conversation.

Your cloud,
documented like
a living system.