Introduction of a central cloud-based authentication
During a working day, a normal user in most companies accesses countless applications and resources and, in many cases, has to juggle different identities. From either a security or a convenience point of view, it makes no sense to leave this task to the user themselves. In the best-case scenario, this is done with a password safe; in the worst case, an all-too-familiar sticky note is stuck to the monitor. IT departments are faced with the challenge of preventing this, providing a centralized solution and offering as much flexibility as possible to support all applications.
With a view to harmonization in particular, it is important to set only one central instance here and to make this the company’s standard, whether it is an on-premises service or a cloud solution. If the company already relies heavily on Microsoft products, then Azure Active Directory (AD) is the ideal successor to the “classic” AD. Modern authentication based on federation technologies, smooth transition from AD and necessary prerequisites for all products from the Microsoft 365 portfolio are just a few of its advantages. In addition, it will also be possible to use other SaaS products from Microsoft in the future, for example with regard to security, without building up your own infrastructure.
Clear application strategy
However, this approach must also be accompanied by a clear application strategy and governance. The 5 Rs (retire, replace, retain, rehost, reenvision) are helpful in assessing what needs to be done and the cost-benefit ratio. Today’s decisions will shape the application landscape for the next 5 to 10 years with regard to business applications and their longevity in particular.
The resulting advantages are:
- Central authentication instance
- True enterprise single sign-on
- Secure application authentication strategy
- Single identity strategy
- Readiness for B2B and B2C scenarios
- Future-oriented cloud & authentication strategy