Building Internal Tools on Microsoft 365

Most pharma and biotech companies are paying for Microsoft 365 E3 or E5 licenses. They're using Outlook, Teams, and maybe SharePoint for document storage. That's roughly 20% of what they're paying for.

Sitting underneath those familiar applications is a full development platform — Azure Active Directory for identity, Microsoft Graph API for data access, Azure Static Web Apps for hosting, Azure Functions for backend logic, and Power Platform for low-code solutions. These aren't add-ons or upsells. They're included in the subscription you're already paying for.

The question isn't whether you have the tools. The question is whether you have someone who can unlock them.

The "Buy Another SaaS" Trap

When a pharma company needs a specific tool — a compliance monitoring dashboard, an internal recruiting portal — the default instinct is to find a SaaS product that does it. For many needs, that's the right call. There are excellent off-the-shelf products for CRM, ERP, project management, and dozens of other business functions.

But there's a category of tools that falls into a gap: specific enough to your workflow that off-the-shelf products don't quite fit, but not complex enough to justify a large custom development project. Internal process tools, department-specific dashboards, compliance tracking systems, and workflow automation that bridges your existing Microsoft 365 apps all fall here.

For these tools, adding another SaaS vendor means another contract, another security review, another integration to maintain, another set of credentials to manage, and another renewal to negotiate. In a regulated industry where every system touchpoint has compliance implications, that overhead is real.

What You Can Build on M365

The Microsoft 365 and Azure platform supports a wider range of internal applications than most IT teams realize. Here are real examples from my own work:

Regulatory Compliance Mailbox Monitor: A monitoring tool for shared regulatory mailboxes that tracks response times, flags overdue items, and provides executive-level visibility into FDA correspondence handling. Built on Azure Static Web Apps with Microsoft Graph API pulling data from Exchange Online. The application authenticates through Entra ID, so there's no separate login — if you can access Outlook, you can access the dashboard.

Internal Recruiting Portal: A centralized application system where candidates submit applications, hiring managers review and track pipeline, and the system integrates with Microsoft 365 calendar and email for interview scheduling. This replaced a workflow that previously lived in shared inboxes and spreadsheets.

Custom HRIS: A full human resources information system tracking employee data, organizational structure, PTO management, and onboarding workflows. Built to replace a third-party HR platform that cost more annually than building the replacement did in total.

Entra-Integrated OrgChart: An org chart that pulls live from Entra ID, so it stays current without anyone manually maintaining it. It reflects reporting relationships, department structures, and role metadata without a separate data sync.

Regulatory Compliance Dashboard: A cross-system view of compliance status, open items, and deadline tracking for the regulatory affairs team — built to surface the information that was previously scattered across email threads, shared drives, and spreadsheets.

The AI Accelerator

Building these applications is significantly faster today than it was even two years ago, because of AI-assisted development. I use Claude Code to describe business requirements and application architecture, then build the implementation collaboratively in a fraction of the traditional timeline.

This shifts the economics meaningfully. A custom internal application that would have required a development team and several months of work can now be delivered by a single experienced IT leader in weeks. The cost to build drops below what many companies pay annually for the SaaS product the custom tool replaces.

Why IT Leadership Matters Here

The technology platform is available. AI has compressed the development timeline. But the missing piece for most companies is someone who understands both the technology capabilities and the business context well enough to connect the two.

Building a regulatory compliance dashboard isn't a pure coding exercise — it requires understanding what FDA correspondence handling actually looks like, what "overdue" means in a regulatory context, and what information an executive needs to make decisions about compliance posture.

That's why this work sits naturally with an IT Director rather than a development shop. I need to be embedded enough in the business to understand the problem, technical enough to architect the solution, and experienced enough with the Microsoft platform to build it efficiently. A development shop can write code. They can't tell you what the tool should actually do.

Getting Started

If you're running a pharma or biotech company on Microsoft 365 and you're frustrated by manual processes, disconnected workflows, or expensive SaaS tools that don't quite fit — start by inventorying your pain points. Which processes involve people copying data between systems? Where are teams relying on shared inboxes or spreadsheets to manage workflows? What reporting do you wish you had but can't get from your existing tools?

Those gaps are the opportunities. And the platform to fill them is already in your subscription.