Skip to content

Latest commit

 

History

History
158 lines (86 loc) · 9.28 KB

readme.md

File metadata and controls

158 lines (86 loc) · 9.28 KB

Configure Conditional Access policies using templates based on Microsoft Graph APIs

Intent: As an IT admin, I want to be able to easily configure Conditional Access policies within my pre-production environment.

You can use the Conditional Access APIs to easily deploy Conditional Access policies in your pre-production environment using Temlates. For example, you can:

As a IT admin, be able to copy a template policy file and configure it in your pre-production environment.

Configure

This automation can be very useful for:

  • Organizations that manages large numbers of Conditional Access policies. OR
  • Identity partners that manages policies for customers.

This tutorial shows how to build a logic app that allows easy configuration of Conditional Access policies using Templates. Specifically, this logic app monitors any policies being pasted in the template folder of OnDrive. If a new policy is detected, an approval workflow is triggered on a Teams channel. Upon approval, the policy is configured in a designated pre-production environment.

In this tutorial, you learn how to:

✔️ Deploy this logic app to your organization.

✔️ Authenticate your logic app to Azure AD with the right permissions.

✔️ Add parameters and connections specific to your organization within logic app.

When you're done, you will be able to manage Conditional Access policies using templates and the following steps within your pre-production environment:

  1. Copy your Template and drop it in your OneDrive folder

    Copy to OneDrive

  2. Approve Template configuration in Teams

    Approve configuration

  3. Receive notification that Template is successfully deployed in your pre-production environment

    Confirmation

  4. View your newly deployed Conditional Access policy in Azure portal

    View policy

  5. Assign your Test users to the policy

    Assign test users

Prerequisites

If you don't have an Azure subscription, create a free Azure account before you start.

You will also need knowledge of key concepts within Azure logic apps, OneDrive and Teams.

Complete the steps in the article Secure authentication for Conditional Access automation to create a Key Vault and connect to Managed Identity.

Step 1: Deploy this logic app to your organization

If your Azure environment meets the prerequisites, and you're familiar with using Azure Resource Manager templates, these steps help you sign in directly to Azure and open the Azure Resource Manager template in the Azure portal. For more information, see the article Deploy resources with Azure Resource Manager templates and Azure portal.

Azure Portal

Select the following image to sign in with your Azure account and open the logic app in the Azure portal:

Logic App for Easy Configuration of Conditional Access Policies using Templates.

Deploy to Azure

  1. In the portal, on the Custom deployment page, enter or select these values:

    Property Value Description
    Subscription <Azure-subscription-name> The name for the Azure subscription to use
    Resource group <Azure-resource-group-name> The name for a new or existing Azure resource group. This example uses AutoPilotConditionalAccess.
    Location <Azure-region-for-all-resources> The Azure region to use for all resources, if different from the default value. This example uses the default value, [resourceGroup().location], which is the resource group location.
    Logic App Name <logic-app-name> The name to use for your logic app. This example uses 301-conditionalaccess-policy-template-automation.

    Here is how the page looks with the values used in this example:

    Provide information for quickstart template

  2. When you're done, select Review + Create and finally Create.

Step 2: Authenticate your logic app to Azure AD with the right permissions

This logic app uses Managed Identity to access secrets from Key Vault to call the Conditional Access APIs. As a prerequisite you must have completed the steps in the article Secure authentication for Conditional Access automation to create a Key Vault and connect to Managed Identity. To learn more about how to use managed identities within Logic Apps, see the article Logic Apps and Managed Identities.

  1. In the left-hand navigation pane, select Identity > User Assigned > Select Add.

  2. Select the User-assigned managed identity from the context pane that appears on the right, select Add.

    Select the identity to authenticate with

Step 3: Update parameters

  1. In the left-hand navigation pane, select Logic App designer > Parameters > Replace the default value with Key Vault URI (storing Client Secret), Client ID and Tenant ID.

    Update the parameters in the Logic App

Step 4: Connect to your OneDrive account and select the template folder you will like to use for automation

  1. On the Logic App Designer, in the OneDrive for Business connection box, click Connections. This example uses OneDrive connector for Logic apps:

    Select "Connections"

  2. If prompted, sign in to your email account with your credentials so that Logic Apps can create a connection to your OneDrive account.

  3. If connection is successful, select the OneDrive folder you would like to use for Template automation.

Step 5: Connect to Teams channel for approving or rejecting Template requests

  1. On the Logic App Designer, in the Teams connection box, click Connections. This example uses Teams connector:

    Select "Connections"

  2. If prompted, sign in to your email account with your credentials so that Logic Apps can create a connection to your Teams account.

  3. Specify the Team and channel you will like to use for automation of approval workflow.

Step 6: Select appropriate managed identity

  1. On the Logic App Designer, in the HTTP connection box, click GET client secret from key vault using managed identity. This example uses HTTP connector.

  2. Specify the Managed Identity to use.

    Select "Managed Identity"

Step 7: Update all other connectors within Logic App

Similar to above, update remaining OneDrive and Teams connectors within the sample Logic App by selecting appropriate OneDrive and Teams account that needs to be used for automation.

Warning

Ensure you follow best practices regarding managing secrets within Logic apps by using secure inputs and outputs as documented in the article, [Secure access and data in Azure Logic Apps]](https://docs.microsoft.com/azure/logic-apps/logic-apps-securing-a-logic-app).

Next steps

Try the following challenge:

✔️ Edit this logic app to send a custom message on Teams channel when the approval workflow selection is Reject action.

✔️ Edit this logic app to delete the policy file in OneDrive template folder when the approval workflow selection is Reject action.

Try creating and updating a Conditional Access policy using the following JSON templates:

Preview features and new functionality are added to Conditional Access regularly, as they are added they become available first in the Conditional Access API beta endpoint.

Next, Configure Safe rollout of policies from pre-production to production with approval workflow.

For more information on the Conditional Access APIs, see the following documents: