Concept
A client secret is a password-like credential an application uses to prove its identity to Microsoft Entra ID; it should be treated as an exception and replaced by managed identities, federation or certificates where possible.
| Type | Concept |
|---|---|
| Also known as | Client secrets, Application secret |
2026-08-05 · Video on YouTube
Apps, pipelines and AI agents need access too, yet many still hide passwords in code and config files. In this Simply Explained episode, Mirko Peters gives Azure admins, developers and architects a plain-English map of Microsoft Entra workload identities…
2026-07-02 · Video on YouTube
Microsoft Graph is far more than just another API—it is the operational backbone of Microsoft 365. This episode explains why relying solely on admin portals limits scalability, visibility, and automation, while Microsoft Graph provides a unified interface for…
2025-08-05 · Video on YouTube
Your Viva rollout isn’t failing—your automation is. Stop hand-typing Topics, chasing Learning content across LMS silos, and waiting for Connections posts to “eventually” appear. Learn the exact auth scopes, payload shapes, and batching tactics to: publish…
2026-07-16 · Video on YouTube
Managed Identities are one of Azure's most powerful security features, yet they're often overlooked. Instead of storing usernames, passwords, client secrets, or certificates inside your applications, Azure can automatically create and manage an identity for…
2025-08-09 · Video on YouTube
Tired of manual, brittle Power Platform deployments? This guide shows how to build a reliable CI/CD pipeline with Azure DevOps that handles the real trouble spots: environment variables, connection references, service connections, and secure secrets. Learn…
2025-08-09 · Video on YouTube
Most Microsoft 365 automations fail for the same reason: they rely on fragile delegated permissions tied to human users—leading to session timeouts, MFA prompts, role changes, and broken jobs. The fix is shifting to app-only permissions with Microsoft Graph…
Register an Entra ID app as a service principal, prefer certificate credentials stored in Key Vault over client secrets, and grant only the required Application permissions for predictable tokens. · From the episode: Automate Viva Connections, Topics, Learning…
Store secrets such as client secrets in Azure Key Vault and link them to Azure DevOps variable groups. Service connections are scoped to each target environment with least privilege, so nothing is hard-coded. · From the episode: Implement Power Platform CI/CD with Azure DevOps
Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.
Nobody has listed this topic yet. Add it to your profile.
Maintained by Mirko Peters (Microsoft MVP) · Last updated:
EN
Deutsch
Español
Français
Italiano
Português
Nederlands
Polski
Bahasa Indonesia
Русский
Українська
العربية
עברית
日本語
한국어