1. Review the systems and users

We start with an inventory of applications, remote access, administrator accounts and working patterns. Shared accounts, older applications and unattended services need particular attention because they may not work like an ordinary staff login.

We agree which systems are in scope, which Duo edition is appropriate and how licensing will work. This gives you a clear proposal before configuration begins.

2. Plan the Microsoft 365 integration carefully

Duo supports Microsoft Entra ID External MFA. The documented Microsoft 365 integration requires a Microsoft subscription that includes Entra ID Premium P1 or P2. Conditional Access can then determine which users and applications require MFA.

We check your existing Microsoft policies and registration methods before adding another provider. The policy design matters just as much as enrolling the phone: an account left outside the intended enforcement can leave a gap.

3. Prepare staff and recovery access

Staff receive clear enrolment instructions and guidance on recognising a genuine request. We agree alternatives for people without a suitable smartphone, plus a process for changing phones or reporting a lost device.

Administrator recovery access should be tightly controlled, documented, monitored and tested. Identity checks are essential before replacing someone’s authentication method. A request that sounds urgent is not enough.

4. Pilot before wider enforcement

A small representative group tests normal work before the rollout expands. That should include staff working remotely and people using any specialist applications.

  • Confirm successful access to each protected application.
  • Check that missing or rejected authentication actually blocks the intended login.
  • Test device replacement and approved recovery procedures.
  • Check supported remote access and offline scenarios where relevant.
  • Record support contacts and a controlled rollback plan.

5. Roll out in stages and keep reviewing

Once the pilot is accepted, we extend the configuration in agreed groups and help staff enrol. Sign in logs and support feedback help identify unexpected prompts or uncovered applications.

Joiners, leavers and changed responsibilities need ongoing attention. We review access and authentication policies as the business changes rather than treating deployment as a one off exercise.

Ready to move to Duo?

Existing clients and new customers can contact Bury I.T. Support Ltd to arrange a Duo implementation review. Tell us roughly how many people need access and which systems you use. We will assess the setup, explain costs and agree a migration plan. Call 0161 884 3303 or use our contact page.

Official sources and further reading

These primary sources were checked when this article was last reviewed.

Written by

Christopher Lomax

Director of Bury I.T. Support Ltd, with more than 20 years of practical experience supporting business IT, Microsoft 365, networks, servers and cyber security.

About the team