Protect your Authentication Tokens with Overe

Protect your Authentication Tokens with Overe
Written by
Paul Barnes
Published on

Token Protection Conditional Access now in Overe

Attackers don’t always breach your environment by breaking MFA or guessing passwords. Increasingly, they take a shortcut: stealing an active session token and bypassing most of your defenses entirely.

In Microsoft 365, these tokens—Primary Refresh Tokens (PRTs)—are issued when users authenticate and allow them to access services without reentering credentials. If a token is stolen, it can often be reused from a different device without triggering your Conditional Access rules.

Microsoft’s Token Protection policy changes this dynamic. When enabled, PRTs are cryptographically bound to the device they were issued to. If the token is copied to another device, it becomes invalid. This prevents attackers from using stolen tokens for lateral movement or persistent access.

Licensing requirement: Token Protection is available with a Microsoft Entra ID P1 license. This is already included in Microsoft 365 Business Premium and Microsoft 365 E3, as well as the standalone Entra ID P1 license, so most organisations can enable it at no extra cost.

Deploy it easily with Overe

Why We’re Adding It to Overe

Keeping up with new Microsoft security features is a moving target.Overe’s role is making sure you don’t miss changes that matter to your environment. Token Protection is now part of Overe’s Conditional Access policy set.

By integrating it into Overe:

  • You can apply it quickly across tenants without manual configuration.

  • You ensure consistent enforcement

  • You are no longer without relying on admins to spot and enable new features.


How Token Protection Works

  • Scope: Applies to sign-ins to supported resources such as Exchange Online and SharePoint Online.

  • Binding: Uses hardware-backed keys to tie the PRT to the originating device.

  • Compatibility: Requires devices that are Entra ID joined or registered and running Windows 10 or later.

  • Enforcement: When the token is presented from an unbound context (different device or tampered environment), access is denied.

Learn more about Token Protection in Microsoft’s documentation
Start with Overe

Overe Newsletter
No spam. Just the latest releases and tips, interesting articles, and exclusive interviews in your inbox every week.
Read about our privacy policy.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.