Setup - Azure Active Directory¶
Looking for Azure setup instructions? To get started with Fugue on Microsoft Azure, see Setup non-Active Directory- Azure & Azure Government.
Looking for Amazon Web Services instructions? To get started with Fugue on AWS, see Setup - AWS & AWS GovCloud.
Looking for Google setup instructions? To get started with Fugue on Google Cloud Platform, see Setup - Google Cloud.
Looking for Repository setup instructions? To get started with Fugue on Repository, see Setup - Repository.
Ready to create a Fugue environment? An environment contains resources from a single AWS account, Azure subscription, Google project, or code repository – in this case, Azure Active Directory. Fugue surveys the resource configuration in an environment and reports whether the infrastructure is compliant with a particular compliance standard.
We recommend only activating Active Directory support for the credentials associated with a single Fugue environment. Your Active Directory resources will show up in this environment and if you add Active Directory permissions in other environments, the resources will be duplicated.
In a hurry? For an even quicker setup guide, see Get Started in 5 Minutes.
To learn more about the basics of using Fugue, see Fugue 101.
Step 1: Setup (Name, Provider)¶
You must have at least one existing resource group in Azure in order to create an environment in Fugue.
In the first step of creating an environment, you name it and specify your provider – cloud or repository.
Name your environment.
Select Azure as the provider, whether you’re using Azure or Azure Government.
Step 2: Settings (Credentials, Resource Groups)¶
If at any point you want to change something, you can select “Back” at the bottom of the page to return to the previous step, or “Edit” in the sidebar next to the desired step to return to that step.
Step 2 has two parts, which we’ll detail next:
Step 2a: Connect to Azure¶
Before Fugue can connect to your Azure subscription and scan your infrastructure, you’ll need to provide four pieces of information:
- Subscription ID
- Tenant ID (directory ID)
The ID of your specific Azure Active Directory instance. To find your tenant ID, log into the Azure Portal and navigate to Azure Active Directory > Properties > Directory ID (or use the Azure Government link).
- Application ID (client ID)
The ID for the Azure Active Directory application you register for Fugue. You’ll create this in the next step.
- Client secret
The secret string Fugue uses to authenticate with Azure. You’ll also create this in the next step.
Create Azure Active Directory Application & Assign the Azure AD Directory Readers Role (for Active Directory resources)¶
To obtain an application ID (client ID) and client secret, you’ll need to create an Azure Active Directory (AD) application and service principal, assign it an RBAC role, and then generate a secret. This gives Fugue the permissions required to scan your selected resource groups.
Enter a name for the AD application – we’ve called ours
fugue-examplein the image below – and then ensure supported account types is set to “Accounts in this organizational directory only.” You can leave the “Redirect URI” field blank. Then, click the “Register” button.
If you want Fugue to manage Active Directory resources such as users and service principals, you must also assign the Azure AD Directory Readers role to your service principal. This action requires a user with Global Administrator or Privileged Role Administrator permissions.
To assign the Directory Readers role, navigate to All services > Azure Active Directory > Roles and administrators (or use the Azure Government link) and click on Directory readers.
On the Directory readers | Assignments page, click Add assignments.
On the Add assignments page, go to the Select members section and click No member selected. In the Select a member panel, choose your service principal. Click Select then Next then Assign. Your service principal should now be listed on the Directory readers | Assignments page under Active assignments.
After Azure registers the application and creates the service principal, you can copy the application ID and enter it into the Fugue environment setup:
Assign an RBAC Role¶
Next, you’ll need to assign the service principal an RBAC role. You can scope the role to your entire subscription, a specific resource group, or an individual resource. If you intend to use Fugue to scan more than one resource group, it’s simplest to give the application access at the subscription level, but go with whatever works best for your use case.
To assign your service principal a role at the subscription level, navigate to Azure Active Directory > App registrations (or use the Azure Government link), and select your subscription. Then, select the Access Control (IAM) link and click the “Add” button, then “Add role assignment”:
Select the Reader role. Leave the “Assign access to” field as is and search for the name of your AD application in the “Select” field, then select the “Save” button.
Generate a Client Secret¶
Now that you’ve created the AD application and set up the service principal, you can generate a client secret. Return to Azure Active Directory > App registrations (or use the Azure Government link) and select the application you just registered, then select the Certificates & secrets link. Click the “New client secret” button and enter a description for your client secret and set an expiration date, then select “Add.” You can then copy the value to the Fugue environment setup:
The Secret ID is not the value you copy and paste into the Client Secret field within Fugue. Use the Value field.
Back in the Fugue environment setup, select the “Connect to Azure” button. You should see a message confirming that the connection was successful:
You can select “Undo” if you need Fugue to connect again and refresh the list of resource groups. Note that when you select “Undo,” Fugue clears all of the credential fields.
Step 2b: Select Resource Groups¶
Now that Fugue has connected to your Azure subscription, you may specify the resource groups you want Fugue to scan.
If you’d like Fugue to scan the infrastructure configuration of all resource groups in your Azure subscription, select Yes for “Include all resource groups?” Note that after the environment is created, Fugue will automatically detect new resource groups and add them to your environment.
If you’d prefer to select the resource group(s) Fugue should scan, you can pick “No - select a subset of resource groups” and check the box for the desired resource groups.
If you want to select a resource group you created in Azure after connecting but before finalizing the environment, you can refresh the list of available resource groups by selecting “Undo” and re-entering the connection information.
To change the selected resource groups after the environment has been created, you must use the Fugue API. See How To: Add or Remove Azure Resource Groups for details.
Step 3: Select Compliance Libraries¶
If you’d like Fugue to evaluate your infrastructure configuration for all compliance standards, ensure “Yes” is selected.
If you’d prefer to select the compliance families yourself, click No - select a subset.
Fugue supports the following compliance families for Azure environments:
Step 4: Review Environment Details¶
Review the details for your environment, including environment name, subscription/tenant/application IDs, compliance standards, and resource groups.
If anything needs to be changed, click Edit next to the appropriate step, as highlighted below.
3. If everything looks good, select the Approve and Begin Scan button. Fugue will create your environment and start to scan your infrastructure.
When the scan is complete, Fugue brings you to your environment’s dashboard, where you can see your compliance state.
Congratulations! You’ve just created an Azure environment with Fugue.
Fugue will continue to scan the resource configuration in your environment at regular intervals (and on demand). This is how Fugue detects compliance violations in your infrastructure.
Now that you’ve created an environment, learn how to configure it further in Environment Configuration. If you’d like to learn more about checking compliance state, see Compliance. Or, check out the visualizer for an interactive diagram of your cloud infrastructure.