Engineering integration guide
Microsoft Azure + UbiGrowth workflows
Microsoft Azure is Microsoft's cloud platform, covering infrastructure, identity, and enterprise application services. This guide covers the records that matter, how the connection should be scoped, and what the first bounded workflow should be.
Introduction
Make Microsoft Azure part of the workflow, not another silo.
Validate connector availability for your workspace
This guide covers how a team designs a engineering workflow around Microsoft Azure with UbiGrowth: which records stay authoritative, how the connection should be scoped, what the first bounded workflow should be, and how to tell whether it worked.
The records that matter are Subscription, Resource Group, Resource, Management Group, Policy, and Cost Management Export. Azure identity is hierarchical — Management Group, Subscription, Resource Group, Resource — and RBAC is inherited down that chain. A role assigned high grants more than the assignment appears to say.
Microsoft Azure is not currently on UbiVibe's verified connector list. This page is an implementation design reference: use it to specify the workflow, then validate whether the connection is available and correctly scoped for your workspace before you make it a dependency. The verified UbiVibe connections today are Salesforce, HubSpot, Gmail, Google Drive, Slack, and GitHub.
The platform layer is the usual destination for this connection, because the value shows up as governed context and execution shared across more than one team.
Why teams evaluate this connection
Integrations create value when they remove operating friction.
The first design decision is not which API endpoint to call; it is which system owns the record, what event should trigger work, who owns the exception path, and what successful completion means.
Engineering systems produce more signal than any other part of the business and the least usable summary. Microsoft Azure knows exactly what happened; turning that into something the rest of the company can act on is manual work that nobody owns.
The second problem is direction of risk. An integration that reads engineering activity is low-risk and useful. An integration that can act on infrastructure or production systems is a different category entirely, and the two are often discussed as if they were the same project.
You're likely here because
- Engineering activity is invisible outside the engineering team
- Incident context has to be reassembled manually every time
- Internal tool requests sit behind product work indefinitely
Record model
What a Microsoft Azure integration actually reads and writes.
Integration design starts from the objects the system really exposes, not from a generic connector diagram. These are Microsoft Azure's.
Identity and matching
Azure identity is hierarchical — Management Group, Subscription, Resource Group, Resource — and RBAC is inherited down that chain. A role assigned high grants more than the assignment appears to say.
Start here
Read Cost Management data by Resource Group and route unattributed spend to the subscription owner.
What this will not do
It will not be equivalent to an AWS integration. The resource model, identity model, and cost surface differ enough that the workflow needs designing separately.
The constraint to plan around
Azure Policy can block resource operations at deployment time, so an integration provisioning resources fails against governed subscriptions in ways that never appear in a sandbox.
Build notes
What you actually have to reason about in Microsoft Azure.
The fields that carry meaning, how the connection authenticates, and whether the event surface can be trusted. This is the part that decides whether the integration works in month three.
| Field | Why it matters |
|---|---|
| resource id | the full hierarchical path — subscription, resource group, provider, name |
| tags | cost attribution, with policy able to enforce them unlike most clouds |
| provisioningState | per-resource lifecycle, and asynchronous operations complete after the API returns |
| RBAC assignment scope | inherited down the hierarchy, so a high assignment grants far more than it reads as |
| Cost Management amortized vs actual | two legitimate cost figures that differ for reserved capacity |
Authentication
Entra ID service principal or managed identity with RBAC assigned at the narrowest scope that works. Managed identity avoids credential handling entirely where the caller runs inside Azure, and should be preferred when available.
Events and delivery
Event Grid carries resource and custom events with retry and dead-lettering. Activity Log records control-plane operations with a delay, and is the audit trail rather than the trigger.
Workflow
How the Microsoft Azure workflow runs.
The operating sequence, from reading the source system through to the result landing back where it belongs.
Step 01
Connect read-only first
Microsoft Azure is connected with scoped, read-only credentials so context and reporting value can be proven without any action risk.
Step 02
Assemble the engineering picture
Delivery, incident, or operational activity is summarized in a form the rest of the business can act on rather than a raw feed.
Step 03
Build the internal surface
Launch produces the dashboard or internal tool that was never going to clear the product backlog, reviewed like any other internal service.
Step 04
Bound any action path
If the workflow needs to act, that path is specified separately with explicit scope, approval, and a record of what ran.
Design decisions
The engineering decisions this connection forces.
Each of these has to be settled before the Microsoft Azure workflow is allowed to write anything.
Step 01
Separate read from act
Reading Microsoft Azure for context and reporting is a different risk decision from letting a workflow act on it. Do not bundle them into one project.
Step 02
Make execution paths explicit
Any action that reaches a real environment should run through a reviewable execution path with a record of what ran, not an implicit side effect.
Implementation path
How to implement the Microsoft Azure workflow.
- 01
Start read-only against Microsoft Azure and produce something the team already wants: delivery visibility, incident context, or an operational summary.
- 02
Use scoped credentials rather than a shared token, and confirm what the scope can actually reach.
- 03
Build the internal surface in Launch, and review the result as you would any other contribution.
- 04
After unattributed-spend routing works, add policy compliance reporting so governance failures surface alongside cost.
Governance
Controls that matter.
Control 01
Credentials are scoped and workspace-approved; no shared secret belongs in a prompt or in generated code.
Control 02
Actions that reach production systems run through explicit, reviewable execution paths.
Control 03
Generated code and configuration are reviewed on the same terms as any other change.
Failure modes
How a Microsoft Azure integration breaks in production.
Not generic integration advice. These follow from how this system actually behaves, which is why they look nothing like the list on the next guide over.
Symptom 01
Resource creation fails only in production subscriptions.
Cause
Azure Policy denies it there and not in the sandbox.
Fix
Surface the policy denial specifically rather than as a generic failure, since the remedy is a policy exemption not a code change.
Symptom 02
An operation returns success but the resource is not ready.
Cause
Many Azure operations are asynchronous and complete after the response.
Fix
Poll the operation status or provisioningState rather than treating the response as completion.
Symptom 03
A role assignment grants far more than intended.
Cause
It was made at subscription or management-group scope and inherits downward.
Fix
Assign at the narrowest scope that works and audit inherited assignments explicitly.
What changes at scale
Throttling is per subscription and per resource provider, with different limits per provider. A sweep needs per-provider concurrency rather than one global setting.
Examples
What a working Microsoft Azure workflow looks like.
Bounded scenarios rather than a feature list. Each one can be verified against work the team already does.
Cloud operations
With Microsoft Azure connected read-only, delivery and operational activity can appear alongside commercial context instead of living in a separate report.
Internal tool that was stuck in the backlog
A small tool reading Microsoft Azure gets built in Launch and reviewed like any other internal service, without consuming sprint capacity.
Limitations and considerations
What to validate before you depend on this.
- Azure Policy can block resource operations at deployment time, so an integration provisioning resources fails against governed subscriptions in ways that never appear in a sandbox.
- Azure Policy can block or modify a write at deployment time, so a call that works in a sandbox subscription is denied in a governed one. Automation that does not surface the policy denial reports an ambiguous failure.
- When an AWS integration is assumed to port. The identity model, resource hierarchy, and cost surface differ enough that the design has to be redone rather than translated.
- Write or action access to Microsoft Azure is a materially different risk decision from read access and should be scoped, reviewed, and approved separately.
- Generated code and configuration still require review. Speed of production does not change ownership of what ships.
FAQ
Microsoft Azure integration questions.
What records does a Microsoft Azure integration actually work with?
The primary records are Subscription, Resource Group, Resource, Management Group, Policy, and Cost Management Export. Azure identity is hierarchical — Management Group, Subscription, Resource Group, Resource — and RBAC is inherited down that chain. A role assigned high grants more than the assignment appears to say.
What should the first Microsoft Azure workflow be?
Read Cost Management data by Resource Group and route unattributed spend to the subscription owner.
What will a Microsoft Azure integration not do?
It will not be equivalent to an AWS integration. The resource model, identity model, and cost surface differ enough that the workflow needs designing separately.
What is the main constraint to plan around?
Azure Policy can block resource operations at deployment time, so an integration provisioning resources fails against governed subscriptions in ways that never appear in a sandbox.
What changes about a Microsoft Azure integration at scale?
Throttling is per subscription and per resource provider, with different limits per provider. A sweep needs per-provider concurrency rather than one global setting.
How does authentication work for Microsoft Azure?
Entra ID service principal or managed identity with RBAC assigned at the narrowest scope that works. Managed identity avoids credential handling entirely where the caller runs inside Azure, and should be preferred when available.
Does Microsoft Azure support webhooks, and can they be trusted?
Event Grid carries resource and custom events with retry and dead-lettering. Activity Log records control-plane operations with a delay, and is the audit trail rather than the trigger.
What is the risk of writing to Microsoft Azure?
Azure Policy can block or modify a write at deployment time, so a call that works in a sandbox subscription is denied in a governed one. Automation that does not surface the policy denial reports an ambiguous failure.
When is connecting Microsoft Azure the wrong call?
When an AWS integration is assumed to port. The identity model, resource hierarchy, and cost surface differ enough that the design has to be redone rather than translated.
What should a Microsoft Azure integration automate first?
Start with one bounded workflow that removes a measurable handoff, duplicate-entry step, reporting delay, or follow-up gap. Expand only after the first workflow is reliable.
Does UbiGrowth require Microsoft Azure to be replaced?
No. The operating model is designed around connecting to systems that should remain authoritative and building workflows around them rather than forcing a wholesale replacement.
Is connector availability identical for every workspace?
No. Availability can depend on provider configuration, authentication, scopes, workspace setup, and deployment state. Validate the required connection before treating it as an operational dependency.
Can the workflow act on Microsoft Azure, not just read it?
Action paths are possible but should be treated as a separate, bounded project with scoped credentials, explicit approval, and a record of what ran.
How are credentials handled?
Through workspace-approved, scoped grants. A shared secret pasted into a prompt or embedded in generated code is not an acceptable pattern.
What is a safe first integration?
A read-only workflow that produces something the team already wants from Microsoft Azure — delivery visibility or incident context — before any action path is considered.
How this access is governed
What ARIA is allowed to do in Microsoft Azure, and who decides.
Connecting Microsoft Azure is a permission decision, not just a setup step. These are the controls that decide what ARIA can reach, what it can change, what gets recorded, and how you take the access back.
Required permissions
ARIA works through the scopes the connection was granted, and no others. Authorization happens at the provider, so the permissions being requested are shown by the system itself before anything is connected.
What it can reach
Reachable systems are the intersection of what your organization approved in the connector registry and what the requesting identity is permitted to use. Identity resolves before execution, not after.
What it can do
Actions run through explicit execution paths with state, spend, and failure boundaries — a bounded worker path rather than an open-ended agent loop with a credential.
Credential handling
Credentials live in the governed connection layer and are resolved through canonical connection identity. They are not pasted into individual workflows, prompts, or generated artifacts.
Action logging
Execution carries state and traces: what triggered the work, which connection it used, and what came back — including an explicit failure when something did not run.
Approval and revocation
Consequential actions can be made to require a person to approve them. Access can be changed or revoked at the connection, and ARIA loses that reach without unpicking the work already completed.
Start with ARIA
Ask ARIA to run this integration.
Describe the outcome you need across this system. ARIA works out the scopes, data, and actions the job requires, and operates inside the access you grant — which you can change or revoke.
- ARIA acts only through the systems and permissions you connect.
- Connections use scoped credentials you can change or revoke.
- Actions are recorded, and consequential ones can require approval.
Start here
Turn the integration into a working business outcome.
Start with ARIA to describe the outcome, then continue into the product path that fits the workflow. Connector availability and required scopes should be validated for the specific workspace before production use.