Internal Developer Platforms (IDPs) - Simply Explained

Internal Developer Platforms promise faster development, less friction, and happier developers—but what exactly is an IDP, and how does it work behind the scenes?In this episode of Microsoft Knowledge Nuggets, Mirko Peters explains Internal Developer Platforms in plain English. We explore how platform engineering turns cloud infrastructure, security rules, automation, and developer tooling into reusable self-service experiences that help development teams build, deploy, and operate applications without starting from zero every time.THE PROBLEM INTERNAL DEVELOPER PLATFORMS SOLVELaunching even a simple application can involve repositories, Azure subscriptions, networking, identities, secrets, CI/CD pipelines, monitoring, permissions, and multiple teams. Instead of focusing on features, developers can spend significant time navigating tickets, documentation, portals, and infrastructure decisions.An IDP provides a self-service front door to approved software-building blocks, connecting developers with the automation, standards, tools, and policies already established by the organization.GOLDEN PATHSGolden paths are approved and repeatable routes for common development tasks. Rather than forcing every development team to design infrastructure from scratch, a golden path provides sensible defaults for repositories, CI/CD, Azure resources, identities, monitoring, security, and other standard requirements.Developers provide only the information that matters—such as the service name, owner, environment, runtime, and approved options—while the platform handles the underlying setup. Good golden paths also provide controlled escape routes for applications with unusual requirements.THE SERVICE CATALOGAs organizations accumulate hundreds or thousands of applications and services, understanding what exists becomes increasingly difficult.A service catalog provides a central map of running software, including ownership, documentation, dependencies, source code, operational status, dashboards, and support information. It helps developers and operations teams quickly answer questions such as who owns a service, where its code lives, what it depends on, and where its monitoring can be found.GUARDRAILS WITHOUT SLOWING DEVELOPERS DOWNSelf-service does not mean unrestricted access.Guardrails build organizational requirements directly into the platform. Microsoft Entra ID can control identity and access, Azure Policy can enforce resource standards, management groups can organize subscriptions, Azure Key Vault can protect secrets, managed identities can reduce password usage, and Microsoft Defender can help identify security risks.The objective is to automatically approve normal, safe workflows while directing unusual or risky requests through the appropriate review process.WHAT HAPPENS WHEN YOU CLICK “CREATE SERVICE”A developer may see only a simple button or form, but one request can trigger a substantial automation chain.The platform can create a repository, generate a standard project structure, configure CI/CD, provision Azure infrastructure, assign permissions, connect monitoring, and automatically create documentation and catalog entries.Instead of describing every technical step, developers describe the desired result and let automation create the required environment.GITOPS, BICEP, TERRAFORM AND AUTOMATIONGitOps can store the desired configuration in Git, providing reviewable and traceable infrastructure changes.Technologies such as Bicep or Terraform can provision infrastructure, while Azure DevOps Pipelines or GitHub Actions can automate testing and deployment. Applications might run on Azure App Service, Azure Kubernetes Service, or other approved environments.These technologies can support an IDP, but none of them individually is the platform.AN IDP IS MORE THAN A DEVELOPER PORTALOne of the biggest misconceptions is that an Internal Developer Platform is simply a portal such as Backstage.The portal can provide the user interface, but the actual platform includes automation, standards, infrastructure, security policies, operational processes, and the people maintaining those capabilities.An IDP also does not replace DevOps engineers, architects, security teams, or cloud teams. Instead, it turns their expertise into reusable paths that development teams can consume repeatedly.HOW TO START WITH PLATFORM ENGINEERINGDo not begin by trying to build an enormous platform.Identify one painful and frequently repeated developer workflow. Create one useful golden path around it. Automate the Azure infrastructure, identity, security, deployment, monitoring, and ownership requirements behind that request.Then measure whether waiting times, tickets, setup failures, and developer friction actually decrease.THE KNOWLEDGE NUGGETAn Internal Developer Platform is an internal self-service system that helps teams build, release, and operate software safely.The essential building blocks are golden paths for common workflows, a service catalog for ownership and discoverability, automation for repeatable provisioning, guardrails for safe choices, identity for access control, and visibility into running services.Before building the portal, build the foundation underneath it.Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support.