For years, Microsoft Teams Rooms and shared devices have relied on traditional username/password authentication- a model that works, but comes with familiar pain points: password rotation, credential leaks, sign‑in failures, and the operational overhead of managing accounts across dozens or hundreds of devices. Microsoft has now introduced Password-less Teams Shared Device Resource Accounts , a significant evolution in how Teams devices authenticate. Instead of storing passwords on devices, each device receives a secure, device-bound credential similar in spirit to Windows Hello for Business that improves security, reduces administrative burden, and increases sign‑in resilience. If you manage Teams Rooms, Teams Panels, or Teams Phones, this is one of the most impactful changes to device authentication in years. Why This Matters Organizations deploying shared meeting devices face three recurring challenges: Password management overhead Rotating passwords across many resource account...

Conditional Access has evolved from a simple MFA enforcement tool into the central identity firewall of Microsoft Entra. It decides who can access resources, under what conditions , and how trust should change in real time . Organizations that treat Conditional Access as an architecture, not a configuration, build dramatically stronger identity security with far less operational overhead. This article outlines how to build a modern Conditional Access strategy and highlights the Entra features that make it possible. 1. Start With Identity Risk, Not MFA A modern strategy begins with understanding identity risk. Before writing policies, map out: Human identity risks Workload identity exposure External user access patterns Legacy protocol dependencies Administrative access pathways Entra features that support this: Identity Protection (user risk, sign‑in risk, token theft detection) Risky sign‑in reports Risk-based Con...

In customer identity, flexibility isn’t just a convenience it’s a requirement. As organizations expand globally and integrate with diverse identity providers, the assumption that every user has (or wants to provide) an email address is increasingly outdated. Microsoft Entra External ID now supports a small but powerful capability: making the email attribute optional during sign‑up when users authenticate through a federated external OIDC provider . This change helps organizations deliver more inclusive onboarding experiences while maintaining strong identity assurance. Why Email Became a Bottleneck By default, Entra External ID expects an email claim during sign‑up. When an external IdP doesn’t provide one, users hit the error: “AADSTS901011: No email address was obtained from the external OIDC identity provider during sign-up.” This is common with: Government or national digital identity systems Enterprise IdPs that rely on employee numbers or unique subject ...