Creating an extended integration for Microsoft Entra ID assets

Sync Oomnitza with Microsoft Entra to gain visibility of virtual machines in subscriptions.

This integration retrieves data from the Virtual Machines endpoint. See Virtual Machines - List All.

Contents

1. Before you start
2. Adding credentials to Oomnitza
3. Adding the integration
4. Mapping fields to Oomnitza
5. Running the integration

Before you start

To add the integration, you must retrieve the following information from Microsoft:

Domain. The fully qualified URL including the name of the protocol. The default URL is https://management.azure.com.

Subscription IDs. GUIDs (Globally Unique Identifiers)  associated with Azure resources.  Type the subscription ID, press enter, and repeat the procedure until you have entered all the subscription IDs. See the Find your Azure subscriptions section.

Adding credentials to Oomnitza

The type of authorization that is used is OAuth2 client credentials.

You must provide the following information to add the credentials to Oomnitza:

• Client ID and secret
• Tenant ID
• Scopes
• Domain

See Get subscription and tenant IDs in the Azure portal and Microsoft identity platform and the OAuth 2.0 client credentials flow.

Make life easier and add your credentials to Oomnitza before you create the integration.  

1. In Oomnitza, click Configuration > Security > Credentials.
2. Click Add new credential (+).
3. Search for the integration, and then click the forward arrow > to select the integration.
4. Enter your client credentials and any other additional information.
5. Click Authenticate. You are prompted to log in to authorize your request.
6. Click CREATE.

Adding the integration

1. In Oomnitza, click Configuration> Integrations> Overview.
2. Click Block view
3. Scroll down to the Extended section for asset integrations.
4. Click NEW INTEGRATION.
5. Select the integration in the sidebar.
6. Click ADD.

Integration details overview

More information is provided about the following fields to help you complete the integration:

Software data

Depending on the asset integration, an option might be available to ingest desktop software information such as the name and version of the software installed on an asset. To view the software information in Oomnitza, you must have the software module. 

Installation types

• Cloud. Store credentials in the Oomnitza cloud.
• Local. Store credentials locally. If you want to sync Oomnitza with vendor applications that require AWS or OAUTH authentication, select cloud as the type of installation. Local installations don't support AWS and OAuth authentication. 

Integration preferences

• Create & Update. Add and update records.
• Create only. Add records.
• Update only. Update records.

Integration details

To review or update the integrations details, click Edit .

When you edit the Integration details section, you can select the name or names of integration contacts.  Integration contacts will receive an in-app notification and an email, when the integration fails, when the integration fails to complete within 24 hours, or when the scheduled integration fails to run.

1. Update the integration name.
2. Select an installation type.
3. For integration preferences, select an option.
4. Enter the name of the integration user.  

Credential details

If you selected Cloud as the installation type, choose one of the following options:

• Select the credentials that were created for the integration.
• Edit the credentials that were created for the integration.
• Create new credentials

Scheduling the integration

By default, data is synced once every day. Change the interval or the time so that the data is streamed when your system isn't busy.

1. Click Edit .
2. Make and save your changes.

Mapping fields to Oomnitza

To map the fields to Oomnitza, click Edit .

  Select Edit integration to add rules for syncing data. Filtering integration results.  

Click SMART MAPPING.

You can add new fields to your integration by selecting Add new field   on the mapping page. 
Creating custom API fields. 

Mapping fields to Oomnitza

Mappable fields

Admin Username
Allow Extension Operations
Boot Diagnostics Enabled
Caching
Computer Name
Connector Sync Time
Create Option
Disk Size (GB)
Exact Version
ID
Location
Name
OS Disk Name
Offer
OS Type
Provisioning State
Publisher
Require Guest Provision Signal
Size
SKU
Storage Account Type
Type
Version

Drag and drop

You can map additional fields to Oomnitza.

1. Drag and drop the fields onto the Add new Oomnitza field area in the Oomnitza column.
2. Rename the field.
3. Make your changes.
4. Save your changes.

Let's say you want to make the Name field the sync key. The Name field represents the Virtual Machine ID.

1. Drag and drop the Name field onto the Oomnitza column.
2. Rename the field to Virtual Machine ID.
3. Select the Unique checkbox.
4. Save your changes.

You can now select Virtual Machine ID as the sync key.

Selecting sync keys

You must select at least one field as the sync key field. To ensure that the sync runs successfully, the field must contain unique values such as the serial number of an asset record or the email address of a user record. Records that do not contain a value for the sync key are skipped.   

See Configuring multiple sync keys.

Running the integration

Launching the integration

Your integration is in Draft mode until the required mandatory fields are added. When added, click Launch to activate your integration. 

If you selected Cloud as the installation type when creating the integration, see Running an extended integration

If you selected Local as the installation type when creating the integration, see Running an extended integration locally.

Viewing data ingested by Oomnitza

Viewing ingested asset data

For asset integrations, click Hardware. If the asset integration also ingests software data, click Software.

Viewing ingested user data

For user integrations, click People. If you chose the option to ingest User and SaaS user data, click Software > SaaS, click the SaaS app, and then click the Users tab. 

Related Links

• Running an extended integration
• Troubleshooting integrations
• Mapping extended integrations