> For the complete documentation index, see [llms.txt](https://agents.glueckkanja.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://agents.glueckkanja.com/agents/privileged-admin-watchdog/changelog.md). # Changelog ### \[1.0.1] - 2025-11-03 Updated the Agent Output. ### \[1.0.0] - 2025-09-30 #### Initial Release First release of Privileged Admin Watchdog! This version provides comprehensive analysis of standing administrative privileges with JIT migration planning. **What's included:** * Standing privilege discovery across Entra ID roles and Azure RBAC * JIT (just-in-time) access migration planning with phased approach * Privilege creep detection showing dormant and excessive permissions * Privilege escalation path analysis for indirect admin access * Time-bound access enforcement validation * Privileged account activity monitoring with anomaly detection * Automated access certification support * De-provisioning script generation (PowerShell, Azure CLI) * Risk assessment scoring with attack surface calculations * Zero trust readiness assessment with maturity scoring * Emergency access account validation and security recommendations * Service principal permission analysis * Integration with Security Copilot for natural language privilege queries --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://agents.glueckkanja.com/agents/privileged-admin-watchdog/changelog.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.