/
Frequently Asked Questions (FAQ) for Entra ID Connect

Frequently Asked Questions (FAQ) for Entra ID Connect

Owned by Rick Munoz
Last updated: Jan 20, 2025

Yes, you can add custom attributes to the generated schema without affecting the import.

Please check out the attribute list within the Entra ID Connect documentation on Confluence.

No. The synced attributes from Microsoft Intune are fixed. However, we are working on enhancing the app to give you better control of which attributes you want to import.

Apps are billed based on the number of users in your Atlassian product. Jira Cloud apps are priced based on the maximum number of Jira product users on your instance. For example, if you have Jira Software (50 users) and Jira Service Management (10 agents) in the same instance, you pay the 50-user price for apps.

Please visit the App’s Marketplace page for more details on pricing.

Note: While this app has features specific to Jira Service Management, the app is technically available across Jira projects. Therefore, the above guidelines for licensing across maximum users still apply.

The pricing structure for cloud apps is as follows:

  • Monthly subscriptions with up to 10 Atlassian product users are billed at a flat rate price.

  • Monthly subscriptions with over ten users are billed per user, starting at the first user.

  • Monthly subscriptions with more than 100 users are billed per user. The table above provides example pricing at various user levels.

Annual subscriptions may offer a discount depending on the number of users purchased.

Depending on how many users and how much data is captured in the attributes, it can take several seconds to several minutes. Due to limitations of the Atlassian Cloud App platform (specifically with Async event limits), Azure AD (Entra) Connect imports 80 user records at a time and waits 3 seconds before starting on the next 80.

By default, No. Any user records removed from Azure AD will still exist in the list of records within Assets.

You can change this by editing the object mapping for the Azure AD (Entra) import in the Asset schema used for the import.

edit object type mapping.png

Specifically, you need to set these two fields in the “Edit Object type mapping” form:

  • Missing Object - set to “Remove”

  • Threshold Number - set to at least 1

object mapping remove.png

 

image-20240209-182610.png

Because the schema is imported into your current Assets instance, there may be a naming collision in your object schemas. The schema generation creates an “Employee Data” and “Employees” object schema to hold the imported data from Azure AD (Entra). If a previous object schema exists (example below), the application will throw an error.

image-20240209-182951.png

In order to rectify this, delete the conflicting object schema from the object schema configuration menu.

image-20240209-183113.png
image-20240209-183127.png

Once the conflicting object has been removed, re-run the Generate Schema and return to your import to confirm the new objects have been successfully created.

image-20240209-183220.png
image-20240209-183419.png

 

IP Allowlisting gives you an additional level of control, allowing you to specify which IP addresses users must use to access content for Jira Software, Jira Service Management, Jira Work Management, and Confluence. You may need to add exceptions for the Azure AD (Entra) Connect app to function properly.

Please contact support for assistance in configuring your installation to work with IP Allowlisting.

Related content