Microsoft Entra ID
Cloud identity as the central directory, with groups that mean something.
Identity is the real perimeter. We centralise it, enforce multi-factor authentication, manage the devices that use it, and make sure the joiner, mover and leaver process is something that happens rather than something documented.

Ask any organization to list its active accounts and compare that against its current staff. The gap is almost always uncomfortable, and it is the single most common way old access becomes a present risk. Centralised identity with a real leaver process closes it.
Cloud identity as the central directory, with groups that mean something.
Where local authentication is still required, including by older applications and instruments.
Synchronised cloud and on-premises identity where both are genuinely needed.
Device enrolment, configuration profiles and compliance policies.
Multi-factor authentication, and conditional access subject to licensing.
A documented process so access is granted, changed and removed on time.
Often not, and dropping it removes a server to maintain. But older line-of-business applications and some instrument software still require local authentication, which is why hybrid exists. We assess what actually depends on it before recommending either.
Badly designed policies will. They are rolled out in report-only mode first, reviewed against real sign-in data, then enforced — and break-glass accounts are configured before anything is switched on.
Only what it is applied to. Legacy authentication protocols can bypass it if they are left enabled, which is one of the first things we check.
Tell us how many users and devices you have and whether MFA is enforced today.
Share the problem, the platform and the deadline. We will come back with an approach, a team and an estimate.