Skip to main content
SyncrionIT

Engineering · Identity and device access controls

Requiring both verified identity and a compliant device for company access

An engineering company needed access decisions to consider both the person signing in and the condition of the device, rather than allowing a correct password to carry the full decision.

Prior experience, completed before SyncrionIT was established in a previous role held by SyncrionIT’s founder. The organization was not a SyncrionIT client; identifying details and certain figures have been generalized.

Phone showing a security lock icon
required for covered users
MFA
encryption checked
BitLocker
device standard verified
TPM 2.0

Scope: The engagement designed and implemented the Conditional Access and Intune controls that connected user authentication, device enrollment, encryption, and compliance status.

What the organization was facing

The company wanted stronger control over who and what could reach company data. A password-only decision could not distinguish between an approved, encrypted company device and an unmanaged device using otherwise valid credentials.

The new controls also had to fit everyday work. A security design that required constant manual exceptions or interrupted legitimate employees would not remain effective for long.

The decision behind the work

The access model joined identity verification with device trust. Covered users would need multi-factor authentication, and the device itself would need to be enrolled, encrypted, and reporting the required compliance state before access was granted.

How the project moved

  1. Strengthen user verification

    Implemented Conditional Access policies requiring multi-factor authentication for the users and company resources included in the project.

  2. Enroll and evaluate devices

    Brought covered devices into Intune so access decisions could use managed compliance information instead of trusting credentials alone.

  3. Require the agreed device baseline

    Configured compliance checks for BitLocker encryption and TPM 2.0 before a covered device could reach company resources.

  4. Enforce the combined decision

    Connected the compliance result to Conditional Access so both verified identity and an approved device state were required.

How the work was checked

  • Confirmed that compliant, enrolled devices could complete the expected sign-in workflow.
  • Confirmed that the policy evaluated device encryption and hardware trust rather than relying only on a successful password and MFA prompt.

What changed

Access to the covered company systems required both a verified user and a compliant, encrypted device. The implemented policy replaced password-only entry with an enforceable identity-and-device decision.

Because Intune supplied the compliance state automatically, the stronger access standard did not depend on someone manually reviewing every ordinary sign-in.

Working through something similar?

Describe what is happening. You do not need to identify the service or technology before contacting SyncrionIT.

CallText