Enforce

Are you looking for information about force configurations in Microsoft Azure and Microsoft 365? In this archive you will find all our posts about force configuration.

  • Microsoft 365

    Exchange Online: Mail encryption with Information Rights Management (IRM)

    Confidential information such as contracts, financial reports, employee or customer data is often exchanged via email. These emails are mostly not encrypted. With Information Rights Management (IRM), encrypted emails can be sent and received between people inside and outside your organization. Sent emails and their replies are encrypted automatically with transport rules or manually from Exchange Online email client (Outlook and Outlook.com). Information Rights Management (IRM) ensures that only intended recipients can open and read the message. It is also possible to prevent emails from being forwarded, printed or parts of them copied. Message encryption works with Outlook, Outlook.com, Gmail and many other popular email services.

    ⟶
  • Microsoft 365,  Microsoft Azure

    Microsoft Authenticator App: Improve security with number matching

    The use of multi-factor authentication is considered one of the most secure methods to protect an account and is therefore recommended by pretty much every provider by now. Due to this fact, the user receives many multi-factor authentication requests every day, which are probably no longer considered carefully and are approved out of habit.Microsoft introduces number matching, a method that can prevent blind approval of the request. For existing users with the Microsoft Authenticator App, number matching will be enabled by default on February 27, 2023.The following tutorial will immediately enable number matching and therefore increase login security.

    ⟶
  • Microsoft Azure

    Microsoft Entra: Roll Over Kerberos Decryption Key

    With Seamless Single Sign-On (Seamless SSO), users can leverage the same credentials for both on-premises and cloud-based services. Repeated authentication prompts between these environments are eliminated, as authentication data is automatically exchanged between Active Directory and Microsoft Entra. As part of the Seamless SSO configuration, a computer account named AZUREADSSOACC is created in the on-premises Active Directory. For security reasons, Microsoft recommends rotating the associated Kerberos decryption key every 30 days.

    ⟶
  • Microsoft Azure

    Azure AD Connect: Enforcing TLS 1.2

    Azure AD Connect no longer supports the following protocols because they are considered insecure. the following services may be affected by the deactivation of the protocols: With TLS 1.2, Azure AD Connect remains executable.

    ⟶