Skip to content

Ulysses Neves

Microsoft Entra ID, authentication, and hybrid identity troubleshooting.

Menu
  • Home
  • Microsoft Azure
  • Microsoft AD FS
  • Microsoft 365
  • Contact
  • Troubleshooting Index
Menu

Microsoft Entra Conditional Access – Configuring Microsoft 365 using a Conditional Access policy

Posted on March 10, 2020

Hello, everyone. In today’s article, we’ll explain what the Office 365 (Preview) application group is and how to use this new feature to control access to Office 365 resources in Azure using a conditional access policy. This configuration is typically used when the administrator wants to block all Office 365 applications except access to email.

What is Office 365 (preview)

Office 365 (preview) is an application group that contains all the resources that make up Office 365 in Azure. Using this group ensures that all applications related to Office 365 will be protected by the configured conditional access policy.

Below we show some applications that are part of the Office 365 (preview) application group:

  • Microsoft Flow
  • Microsoft Forms
  • Microsoft Teams
  • Office 365 Exchange Online
  • Office 365 Sharepoint Online
  • Office 365 Yammer and others.

Creating the conditional access policy

For this illustration, let’s create a conditional access policy to block any access to Office 365 applications and allow only access to email.

To create the new conditional access policy, access the Azure AD > Security > Conditional Access Policy menu or click this link.

Click + New policy.

Fill in the policy name in the Name field.

Selecting the users

To configure the users to be affected by this policy, perform the steps below:
1 – Select the Users and groups menu.
2 – Check the Select users and groups option.
3 – Click Select.
4 – Select the user or group you want to apply the policy to.

Click Select and then Done.

Configuring the applications

Now let’s select all the Office 365 applications listed in the introduction of this article using just one application group, Office 365 (preview). To do this, perform the steps below:
1 – Select the Cloud apps or actions menu.
2 – Click Select apps.
3 – Click Select to select the application group.
4 – Let’s search for the name Office 365.
5 – Select the Office 365 (preview) application.

Click Select.

Excluding Exchange Online from the policy

Let’s configure Exchange Online to be the only Office resource allowed access. To do this, perform the steps below:
1 – Select the Exclude option.
2 – Click Select excluded cloud apps.
3 – Let’s search for the Exchange service.
4 – Select the Office 365 Exchange Online service.

Click Select and then Done.

Configuring the policy control

To select the control to be applied when the user accesses the applications configured in this policy, select the Grant option in the Access controls menu.

For this illustration, let’s block access for users who meet the requirements of this policy.

Click Select.

Let’s enable the policy in the Enable policy option.

Click Create.

Testing the access policy

Now let’s test access to the Office portal through the address https://portal.office.com.

Let’s enter the credential of the user who is in scope for this policy and click Next.

As expected, access to the Office portal is BLOCKED.

Now let’s access the same user’s email directly through the address https://outlook.office365.com/.

We fill in the user’s information again and click Next.

As we can see, access to email is granted.

Checking the access logs in the Azure portal

Let’s confirm through the logs in the Azure portal whether the conditional access policy we created was effective.

You can access the Microsoft Entra ID Sign-ins page using this link.

In the image below we can confirm the error code 53003 – Access has been blocked due to conditional access policies.

When we select the Conditional Access tab, we confirm the policy result for this access: Failure.

Now let’s confirm access to the Office 365 Exchange Online service by selecting the event for this access.

We notice that the status is Success.

Accessing the Conditional Access tab, we confirm that the conditional access policy was not applied, and for this reason, the user’s access to the resource in Azure was granted.

Summary

In today’s article we presented the Office 365 (Preview) feature and how to use this feature to reduce the number of applications listed in the conditional access policy. We demonstrated step by step how to block access to Office applications with the exception of users’ email service.

I hope this content has helped enrich your knowledge of Microsoft Entra ID.

Did you like the post? Like it and share it. 🙂

If you have any suggestions or comments, let us know.

[ ]’s

Ulysses Neves

Related guides: Browse the Microsoft Identity Troubleshooting Index or the Microsoft Entra Conditional Access topic archive.

2 thoughts on “Microsoft Entra Conditional Access – Configuring Microsoft 365 using a Conditional Access policy”

  1. Tiago Rocha says:
    June 18, 2021 at 14:22

    Boa tarde!
    ótimo post.
    duas dúvidas:
    É possível bloquear por horário espeificos?
    É possivel bloquear todos os aplicativos apenas de dispositivos mobile?

    Reply
    1. Uneves says:
      June 18, 2021 at 15:07

      Olá Tiago, obrigado pelo feedback. Seguem as respostas às suas dúvidas:
      É possível bloquear por horário espeificos? Infelizmente ainda não.
      É possivel bloquear todos os aplicativos apenas de dispositivos mobile? É possível configurar a política para sistemas operacionais mobile. Dá uma olhada neste doc: https://docs.microsoft.com/en-us/azure/active-directory/conditional-access/concept-conditional-access-conditions#device-platforms

      Forte abraço.

      Reply

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Recent Posts

  • Microsoft Defender for Identity domain investigation: six questions to ask first September 10, 2026
  • Microsoft Entra Kerberos key rotation: what changes—and what administrators should check September 6, 2026
  • Microsoft Authenticator Will Block Jailbroken Devices in 2026 — What You Need to Know March 17, 2026
  • Enhancing Azure role activation security with FIDO2/Passkeys September 23, 2024
  • Microsoft Entra ID CAP | Enforcing WHfB using Authentication Strength April 21, 2024

Archives

  • September 2026
  • March 2026
  • September 2024
  • April 2024
  • February 2024
  • December 2023
  • September 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • December 2021
  • November 2021
  • October 2021
  • September 2021
  • August 2021
  • July 2021
  • June 2021
  • May 2021
  • April 2021
  • March 2021
  • February 2021
  • January 2021
  • December 2020
  • November 2020
  • October 2020
  • September 2020
  • August 2020
  • July 2020
  • June 2020
  • May 2020
  • April 2020
  • March 2020
  • February 2020
  • January 2020
  • December 2019
  • November 2019
  • October 2019
  • September 2019
  • August 2019
  • July 2019

Tags

#aaddownleveldevice #adfs #adfscertificate #adfscertificates #adfsmfaadapter #azureauth #azureCA #azuredevice #capolicy #cloudsummit2021 #conditionalaccess #conditionalaccesspolicy #deviceregistration #farmbehavior #gopasswordless #mfaserver #msidentity #namedlocation #securingazure #securingazuread #sslprivatekey #troubleshootingadfs #troubleshootingwaptrust #tshootadfs #waptrust #webapplicationproxy #WHFBcerttrust #whfbdeployment #WHfBhybridsetup #WHfBprovisioning #widdatabase adconnect AD FS authenticationstrength az500 azurepim Azure security cloudsecurity microsoft365 Microsoft Azure Microsoft Entra hybrid join Microsoft Entra ID Microsoft Entra MFA PowerShell WHfB
©2026 Ulysses Neves | Design: Newspaperly WordPress Theme
Ulysses Neves
Gerenciar Consentimento de Cookies
Para fornecer as melhores experiências, usamos tecnologias como cookies para armazenar e/ou acessar informações do dispositivo. O consentimento para essas tecnologias nos permitirá processar dados como comportamento de navegação ou IDs exclusivos neste site. Não consentir ou retirar o consentimento pode afetar negativamente certos recursos e funções.
Funcional Always active
O armazenamento ou acesso técnico é estritamente necessário para a finalidade legítima de permitir a utilização de um serviço específico explicitamente solicitado pelo assinante ou utilizador, ou com a finalidade exclusiva de efetuar a transmissão de uma comunicação através de uma rede de comunicações eletrónicas.
Preferências
O armazenamento ou acesso técnico é necessário para o propósito legítimo de armazenar preferências que não são solicitadas pelo assinante ou usuário.
Estatísticas
O armazenamento ou acesso técnico que é usado exclusivamente para fins estatísticos. O armazenamento técnico ou acesso que é usado exclusivamente para fins estatísticos anônimos. Sem uma intimação, conformidade voluntária por parte de seu provedor de serviços de Internet ou registros adicionais de terceiros, as informações armazenadas ou recuperadas apenas para esse fim geralmente não podem ser usadas para identificá-lo.
Marketing
O armazenamento ou acesso técnico é necessário para criar perfis de usuário para enviar publicidade ou para rastrear o usuário em um site ou em vários sites para fins de marketing semelhantes.
  • Manage options
  • Manage services
  • Manage {vendor_count} vendors
  • Read more about these purposes
Ver preferências
  • {title}
  • {title}
  • {title}