TABLE OF CONTENTS

• Overview
• Steps of Configuration
• Azure Details
  • 1. Register an Application in Azure AD
  • 2. Create a Client Secret
  • 3. Find Your Azure TenantID
• Important Notes
• Outcome

Overview

The Azure platform integrates with most well-known Network Devices, or “Remediators,” through their APIs. At the start, the user provides the remediator credentials. The platform then uses these credentials to push policies according to the remediation rules. The user must ensure the credentials have the required privileges so the platform can take the necessary actions. Users add these credentials once in the Remediator screen, located under the Administration section of the UI.

Steps of Configuration

1. Login on the Tenant and go navigate to Administration > Remediator Tab.
2. Click on Add. Complete the required fields.
   1. Device Category: Identity.
   2. Devices: Azure AD.
   3. Device IP: Leave it blank.
   4. User Name/Access ID: Add the client_id here.
   5. Password/Secret Key: Add the client_secret here.
   6. Confirmed Password/Secret Key: Same as the first one.
   7. Name: Add a meaningful name here.
   8. CCE IP: CCE IP on which the remediator is being configured.
   9. Config: {"azureTenantID":"Value of azureTenantID"}
      
3. Click Save.

Azure Details

To get the client_id, client_secret, and tenantID from Azure, you typically need to register an application in Azure Active Directory (Azure AD). This process involves creating an application registration, which then provides you with the client_id. You can then create a secret for that application, which serves as the client_secret. The Azure tenantID can be found in the Azure Active Directory information.

Below is a step-by-step guide: 

1. Register an Application in Azure AD

1. Sign in to the Azure Portal: Go to https://portal.azure.com and log in with your Azure account.
2. Navigate to Azure Active Directory: Find Azure Active Directory (Microsoft Entra ID) in the side menu. If you don’t see it, use the search bar.
3. Go to App Registrations: Click on “App registrations” in the Azure AD menu.
4. New Registration: Click on “New registration” at the top.
5. Create your application:
   1. Enter a name for your application.
   2. Choose who can use the application.
   3. Optionally, enter a Redirect URL (if your application requires one).
   4. Click on “Register”.
6. After registration, you will be directed to your application’s overview page, where you can find the Application (client) ID; this is your client_id.

2. Create a Client Secret

1. Certificates & Secrets: In your application’s menu on the Azure portal, click on “Certificates & secrets”.
2. New Client Secret: Click on “New client secret”.
3. Add a Description and Expiry: Give your secret a description and choose an expiry period that suits your application's needs.
4. Save: Click on “Add”.
5. After you click “Add”, the value of the client secret will be displayed. Make sure to copy the client_secret value now; you won’t be able to retrieve it again once you leave this blade.

3. Find Your Azure TenantID

1. Azure Active Directory: Navigate back to the Azure Active Directory overview page.
2. Properties: Click on “Properties” in the Azure AD menu.
3. Directory ID: On the properties page, you’ll find the Directory ID. This is your Azure tenantID.

Important Notes

• Security: Keep your client_secret secure. Do not share it or commit it to source code repositories.
• Permissions: Depending on what your application needs to do, you might have to set permissions. This can be done in the “API permissions” section of your application in Azure AD. 

The permissions in the snapshot below should be granted:

URL: This is important for web applications that need to authenticate users; it's where Azure AD will return any security tokens.

Following these steps will help you set up an application in Azure AD and obtain the necessary client_id, client_secret, and Azure tenantID for your application to authenticate and authorize against Azure services.

Follow these steps to test the connection:

1. Click on Test Connection.
2. Check on device status by clicking on Test Status.

Outcome

The outcome should show success, the snapshot attached here gives you an example: