Microsoft Azure

Azure that connects your systems and can be supported

We use Azure to connect Dynamics 365, portals and line-of-business systems, host custom applications and move workloads off ageing servers, with monitoring built in from day one.

What it covers

Service BusLogic AppsAzure FunctionsAPI ManagementEntra IDApp ServiceApplication Insights
About Microsoft Azure

What it is

Microsoft Azure is Microsoft’s cloud platform. Around Dynamics 365 and custom applications, it is usually the integration and hosting layer: where systems exchange messages, identity is managed and applications run.

A good fit when

  • Systems exchange data through files, scripts or manual re-keying
  • An integration fails and nobody knows until a customer calls
  • Applications still run on servers that are hard to patch
  • You need single sign-on across staff and customer systems
What we do

How we work with Microsoft Azure

Integration

Event-driven integration with Service Bus, Logic Apps and Functions, with retries, dead-letter handling and correlation IDs.

APIs

API Management in front of internal services, with authentication, throttling and versioning.

Identity

Entra ID single sign-on, app registrations, and Entra External ID for customer and partner access.

Hosting and migration

App Service, containers and Azure SQL for custom applications, and moving older workloads off on-premises servers.

Questions

Common questions about Microsoft Azure

Which Azure regions do you use?

For Australian organisations we design for the Australian regions, such as Australia East and Australia Southeast, so data stays onshore, unless your requirements say otherwise.

Should we use Logic Apps or Azure Functions?

Logic Apps suit orchestration and connector-heavy workflows. Functions suit custom code and high-volume processing. Most integrations use both.

How do you monitor integrations?

With Application Insights and Azure Monitor, using one correlation ID per message so a failure can be traced from end to end and replayed.