Procedural Topic (2)
Finding the Object ID for Your Entra OIDC Application – GitHub
👥 Enterprise Admins 🎯 Reduced support tickets 📅 2024
Reduced setup friction and support escalations by documenting a critical but previously undocumented prerequisite for OIDC token configuration.
Impact
This procedural article filled a critical documentation gap for enterprise administrators configuring token lifetime policies for GitHub Enterprise Managed Users. By providing a validated workflow and example Graph API query, the article reduced setup friction and lowered support escalations related to OIDC session lifetime configuration. The content also improved cross-product accuracy by aligning GitHub’s instructions with Microsoft’s current Entra documentation and API behavior.
At a Glance
Enterprise administrators managing IAM for GitHub Enterprise Cloud
Document missing prerequisite step; reduce configuration errors; align with Microsoft standards
Subject matter experts, product owner
Git/GitHub, Markdown, Liquid, YAML, docs-as-code
View the Work
Screenshots captured October 2025.Screenshots (click to expand)


Behind the work (click to expand)
>Context:
Enterprise administrators configuring Enterprise Managed Users (EMU) with Microsoft Entra OIDC needed to locate the object ID for their OIDC application—a prerequisite for setting token lifetime policies. This essential step was undocumented, causing setup delays and support escalations. The article is part of the larger EMU documentation set, which helps administrators integrate external identity providers like Entra ID and PingFederate.
Activities:
- Collaborated with subject matter experts to validate technical requirements and ensure accuracy
- Researched, tested, and verified steps by navigating Microsoft Entra UI and API workflows
- Authored task-oriented procedures with concrete examples tailored for enterprise administrators
- Created sample Graph API query to reduce trial-and-error during implementation
- Reviewed and revised content to align terminology and style with both GitHub and Microsoft documentation standards </details>