What we do
Tools
Industries
Department
How we workLet's talk →
Home/Azure Developer for Apps Tied to Microsoft 365
Azure Development

Azure Developer Work That Survives a Change on the Microsoft 365 Side

Monday morning the customer portal won't sign anyone in, and the overnight Dynamics sync didn't run. Nobody touched Azure. A secret on the app registration expired over the weekend, or IT switched on a new sign-in policy. Most Azure apps in a Microsoft shop depend on Entra ID and Microsoft 365 more than on the Azure resources themselves, and that's where the hiring decision really sits.

When the Azure app breaks and nobody changed Azure

Each of these starts outside the Azure portal, in Entra ID, Microsoft 365 or a support date, which is why the person who only knows the Azure resources can't find it.

A client secret on the app registration expired

How you'll know: Sign-in or a background job fails with AADSTS7000222, saying the client secret keys are expired. It worked fine on Friday.

Fix: Where the code runs inside Azure, drop the secret and use a managed identity. Where it can't, keep the credential in Key Vault with an alert well before it expires, and write down who renews it.

A new sign-in policy blocked a service account

How you'll know: A scheduled job that logs in with a real user's name and password starts failing after IT turns on MFA or a new Conditional Access policy.

Fix: Replace the user login with an app identity, a managed identity or a service principal, granted only the permissions that job needs. Policies aimed at people then stop catching it.

Code still calling Azure AD Graph

How you'll know: Lookups against graph.windows.net for users, groups or licenses fail, and the app can't read who belongs to which team.

Fix: Azure AD Graph is retired. The calls get rewritten against Microsoft Graph, with the permissions re-consented by an admin.

Functions still on the in-process model

How you'll know: The function app's FUNCTIONS_WORKER_RUNTIME setting says dotnet rather than dotnet-isolated. Support for that model ended on 10 November 2026. It keeps running, but without security updates.

Fix: Move it to the isolated worker model on .NET 10, as Microsoft's migration guide recommends, then test each trigger and binding before the swap goes live.

The mailbox the app sends from lost its license

How you'll know: Order confirmations or alerts stop going out after someone leaves and their account is cleaned up.

Fix: Send from a shared mailbox through Microsoft Graph, with app permissions limited to that one mailbox, so no person's account is holding the process up.

What the job is, and the Azure services it usually lands on

Most Azure work in a Microsoft 365 business is one of these. The right-hand column is where the hidden work sits.

What you need built Usually built on Watch for
A scheduled sync between Dynamics 365 and another system Azure Functions on the isolated worker, or Logic Apps It should run as a Dataverse application user with its own security role, not as an employee's login.
An internal web app staff sign into with work accounts App Service with Entra ID sign-in Access by Entra group, so adding someone to the right group is all it takes, and leavers lose access the day IT disables them.
Microsoft 365 data (Teams, Outlook, SharePoint) feeding another tool Microsoft Graph, called from a Function Admin consent for each permission, kept to the least the job needs. Broad read-all permissions get flagged in security reviews.
Messages between systems that must not be lost Service Bus with Functions reading the queue The dead-letter queue. Messages that fail land there quietly, and they need an alert and someone who looks at them.
A reporting database other tools read from Azure SQL Database Network access. Firewall rules opened wide to get a report working tend to stay that way.

Azure experience, AWS experience, and the Microsoft half of the job

The cloud ideas carry over between Azure and AWS: queues, functions, managed databases, infrastructure written as code. What doesn't carry over is identity. On Azure, almost every app signs in through Entra ID, often uses the same tenant as Microsoft 365, and is governed by policies set by whoever runs your IT. A developer who knows App Service but not app registrations, consent and Conditional Access will build something that works until the first policy change.

n-frames builds and takes over Azure applications for businesses that run Microsoft 365 and Dynamics 365, usually in C# on .NET, with the deployment pipeline set up the way a DevOps engineer would expect. The backend code, the identities it runs under, and the Microsoft 365 pieces it reads from are handled as one job.

Questions people ask

Does Azure work require knowing the rest of the Microsoft ecosystem?

Usually, yes. If you run Microsoft 365 or Dynamics 365, your Azure apps almost certainly sign in through the same Entra ID tenant and read data through Microsoft Graph or Dataverse. Most outages in a Microsoft 365 shop start there, not in the Azure resources, so whoever builds the app has to understand both halves.

Is Azure work different from AWS developer work?

The building blocks are similar, and someone strong on one can learn the other. The services, the tooling and especially identity differ enough that experience doesn't transfer one for one. If you're already committed to Azure because of Microsoft 365, hire for Entra ID and Graph experience as much as for Azure itself.

What if we're not sure Azure is still the right platform?

Then that question gets answered before anything is built. If most of your business runs on Microsoft 365 and Dynamics, Azure is usually the easier home because identity is already there. If you chose it because of a Microsoft deal that's since ended, and nothing you run depends on Entra ID, another platform may cost less. Our quote says which way the evidence points.

Our Azure Functions still run on the in-process model. Do we have to move them?

Support for the in-process model ended on 10 November 2026. Your functions keep running, but they no longer get security or feature updates. The move is to the isolated worker model on .NET 10. For most apps it's a contained job: project file and startup changes, then a careful test of every trigger and binding.

Let's talk

Azure apps that keep running after IT changes a policy

n-frames rebuilds the fragile parts of Azure apps in Microsoft shops: secrets replaced with managed identities, Azure AD Graph calls moved to Microsoft Graph, and Functions moved off the in-process model, each tested against the Microsoft 365 and Dynamics setup you actually run.

Swap secrets for managed identities →

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.