Microsoft Intune

Register Graph API app on Azure AD

• Sign into the Azure Portal.
• If you have access to multiple tenants, use the Directories + subscriptions filter  in the top menu to switch to the tenant in which you want to register the application.
• Search for and select Azure Active Directory.
• Under Manage, select App registrations > New registration.
• Enter a display Name for your application. Users of your application might see the display name when they use the app, for example during sign-in. You can change the display name at any time and multiple app registrations can share the same name. The app registration's automatically generated Application (client) ID, not its display name, uniquely identifies your app within the identity platform.
• Specify who can use the application, sometimes called its sign-in audience.
• Don't enter anything for Redirect URI (optional). You'll configure a redirect URI in the next section.
• Select Register to complete the initial app registration.

• When registration finishes, the Azure portal displays the app registration's Overview pane. You see the Application (client) ID. Also called the client ID, this value uniquely identifies your application in the Microsoft identity platform.
• Your application's code, or more typically an authentication library used in your application, also uses the client ID. The ID is used as part of validating the security tokens it receives from the identity platform. 

Add a redirect URI

A redirect URI is the location where the Microsoft identity platform redirects a user's client and sends security tokens after authentication.

Configure platform settings

Settings for each application type, including redirect URIs, are configured in Platform configurations in the Azure portal. Some platforms, like Web and Single-page applications, require you to manually specify a redirect URI. For other platforms, like mobile and desktop, you can select from redirect URIs generated for you when you configure their other settings.

To configure application settings based on the platform or device you're targeting, follow these steps:

1. In the Azure portal, in App registrations, select your application.
2. Under Manage, select Authentication.
3. Under Platform configurations, select Add a platform.
4. Under Configure platforms, select the tile for your application type (platform) to configure its settings.

5. Select Configure to complete the platform configuration.

Platform	Configuration settings
Web	Enter a Redirect URI for your app. This URI is the location where the Microsoft identity platform redirects a user's client and sends security tokens after authentication. Select this platform for standard web applications that run on a server.
Single-page application	Enter a Redirect URI for your app. This URI is the location where the Microsoft identity platform redirects a user's client and sends security tokens after authentication. Select this platform if you're building a client-side web app by using JavaScript or a framework like Angular, Vue.js, React.js, or Blazor WebAssembly.
iOS / macOS	Enter the app Bundle ID. Find it in Build Settings or in Xcode in Info.plist. A redirect URI is generated for you when you specify a Bundle ID.
Android	Enter the app Package name. Find it in the AndroidManifest.xml file. Also generate and enter the Signature hash. A redirect URI is generated for you when you specify these settings.
Mobile and desktop applications	Select one of the Suggested redirect URIs. Or specify a Custom redirect URI. For desktop applications using embedded browser, we recommend https://login.microsoftonline.com/common/oauth2/nativeclient For desktop applications using system browser, we recommend http://localhost Select this platform for mobile applications that aren't using the latest Microsoft Authentication Library (MSAL) or aren't using a broker. Also select this platform for desktop applications.

Add credentials

Credentials are used by confidential client applications that access a web API. Examples of confidential clients are web apps, other web APIs, or service-type and daemon-type applications. Credentials allow your application to authenticate as itself, requiring no interaction from a user at runtime.

You can add both certificates and client secrets (a string) as credentials to your confidential client app registration.

Add a certificate

Sometimes called a public key, a certificate is the recommended credential type because they're considered more secure than client secrets.

1. In the Azure portal, in App registrations, select your application.
2. Select Certificates & secrets > Certificates > Upload certificate.
3. Select the file you want to upload. It must be one of the following file types: .cer, .pem, .crt.
4. Select Add.

Add a client secret

Sometimes called an application password, a client secret is a string value your app can use in place of a certificate to identity itself.

Client secrets are considered less secure than certificate credentials. Application developers sometimes use client secrets during local app development because of their ease of use. However, you should use certificate credentials for any of your applications that are running in production.

1. In the Azure portal, in App registrations, select your application.
2. Select Certificates & secrets > Client secrets > New client secret.
3. Add a description for your client secret.
4. Select an expiration for the secret or specify a custom lifetime.
   • Client secret lifetime is limited to two years (24 months) or less. You can't specify a custom lifetime longer than 24 months.
   • Microsoft recommends that you set an expiration value of less than 12 months.
5. Select Add.
6. Record the secret's value for use in your client application code. This secret value is never displayed again after you leave this page.

 Add a federated credential

Federated identity credentials are a type of credential that allows workloads, such as GitHub Actions, workloads running on Kubernetes, or workloads running in compute platforms outside of Azure access Azure AD protected resources without needing to manage secrets using workload identity federation.

To add a federated credential, follow these steps:

• In the Azure portal, in App registrations, select your application.
• Select Certificates & secrets > Federated credentials > Add a credential.
• In the Federated credential scenario drop-down box, select one of the supported scenarios, and follow the corresponding guidance to complete the configuration.
• Customer managed keys for encrypt data in your tenant using Azure Key Vault in another tenant.
• GitHub actions deploying Azure resources to configure a GitHub workflow to get tokens for your application and deploy assets to Azure.
• Kubernetes accessing Azure resources to configure a Kubernetes service account to get tokens for your application and access Azure resources.
• Other issuer to configure an identity managed by an external OpenID Connect provider to get tokens for your application and access Azure resources.

Give permissions to the App

Apply the below permissions to this app (both “Application” and “Delegated “):

• DeviceManagementManagedDevices.Read.All
• DeviceManagementConfiguration.Read.All
• User.Read

Below are the details that need to be captured for integration.

To pull logs, we would require:

• App ID/ClientID
• Directory (tenant ID)
• App Secret

Configuring a feed in Chronicle Instance

To configure a feed in Chronicle,

1. From your Chronicle instance page, select Settings from the main menu at top left of your screen

2. Click on Feeds where you can find the data feeds that you have configured as well as the default feeds that Google provided.

3. From the Feeds page, click ADD NEW at top of the screen. The ADD FEED window appears.

4. In Set Properties tab, select SOURCE TYPE as Third Party API from the dropdown menu

5. Select the Log Type as Microsoft Intune from the dropdown menu.

6. Click Next.

7. Now you should fill the required fields as shown in below snip.

8. Click NEXT.

9. In Finalize tab, review the feed configuration that you have provided. Click SUBMIT. Chronicle starts and completes validation check for the new feed. If the validation is successful, a name is generated for the feed and Chronicle attempts to fetch the data.