TABLE OF CONTENTS
Intune Connector Overview
The ManagementStudio Intune connector integrates with Microsoft Intune, enabling administrators to import and manage device, application, and user data within ManagementStudio. The connector requires an Azure App registration with the appropriate permissions. For instructions on creating this Azure App, refer to the Azure App Creation Guide.
Administrators can enable or disable each configuration panel within the Intune Connector according to project requirements.
Best Practice Guidelines
For guidance on best practices when configuring or operating the Intune Connector, see the Best Practice Guidelines.
Intune Connector Panels
Intune Discovery Status
The Intune Discovery Status panel displays and manages the discovery process for Intune data.
| UI Element | Description |
|---|---|
Run Intune Discovery Now | #1 Run the Intune discovery process immediately. |
Schedule Intune Discovery #1 | #2 Set a scheduled time for Intune discovery. For instructions, see Scheduled Tasks. |
Schedule Intune Discovery #2 | #3 Set an additional schedule for Intune discovery (secondary schedule). See above article for configuration steps. |
Last Discovery Date | #4 Timestamp of the last successful Intune connector run. |
Azure TenantId | #5 Specify the Microsoft 365 Tenant ID. See how to find your Azure AD tenant ID. |
App Client Id | #6 Enter the Application (Client) ID assigned by Azure AD during app registration. Details are available in this article. |
Email logs To | #7 Email addresses to receive sync logs. Separate multiple addresses with a semicolon (e.g., user1@domain.com;user2@domain.com). |
Overall Progress | #8 Displays the overall progress of the sync process. |
Current Task Progress | #9 Displays the progress of the current task being processed. |
Import Log | #10 Displays connector logs for review and troubleshooting. |

Import Managed Applications
This panel manages apps provisioned and deployed via Intune.
| UI Element | Description |
|---|---|
Don't Update Locked Apps | #1 Prevents updates to application records locked in ManagementStudio. Not related to Intune app locking. |
Auto Accept New Managed Apps | #2 Automatically accepts new managed applications detected via Intune. |
Platform Filter | #3 Limits imported managed applications to those matching the selected platform. |
Apps Field Mappings | #4 Defines the mapping of Azure AD fields to ManagementStudio fields. Common mappings are created by default. - Target: Field in ManagementStudio (Detail Field, Custom Field, or Blueprint). - MS Field: Path or name used in ManagementStudio. - Intune Field: Attribute of an Intune Application object. Supported transformations are available. |
Add Intune Applications to Blueprint | #5 Adds imported Intune applications to a specified Blueprint. |
App Blueprint Root | #6 Defines the root location for application Blueprints. |

Import Discovered Applications
Applications discovered by Intune on users' devices (typically via Add/Remove Programs). It is recommended to import only apps with a valid Vendor.
| UI Element | Description |
|---|---|
Import Store Applications | #1Include Microsoft Store-installed apps in the import. |
Platform Filter | #2 Import discovered applications by selected platform. |
Force Import ARP Apps with no vendor | #3 Imports Add/Remove Program apps without a Vendor value. Not recommended. |
Add Intune Applications to Blueprint | #4 Adds discovered applications to a specified Blueprint. |
App Blueprint Root | #5 Defines the root Blueprint location for discovered applications. |

Import Devices
Controls which devices are imported and how they are filtered.
| UI Element | Description |
|---|---|
Device Last Activity , X Days | #1 Import devices with Azure activity within the last X days. Use 0 to disable this filter. |
Filter by OS Name | #2 Limit imported devices to selected operating systems. |
Filter By Ownership | #3 Filter imported devices based on ownership type (e.g., Corporate, Personal). |
Exclude Devices (Hostname filter) | #4 Exclude devices whose hostnames match the specified filter criteria. |
Only Include Devices (Hostname filter) | #5 Import only devices with hostnames matching a comma-delimited filter list. Use * as a wildcard (e.g., PC00001, PC00*, *Test*). |

Device Update Options
Configure device sync and field mapping options.
| UI Element | Description |
|---|---|
Don't Update Locked Devices | #1 Prevents modification of ManagementStudio device records that are locked. Not related to device locking in Intune. |
Device Field Mappings | #2 Maps Intune device fields to ManagementStudio fields. Common mappings are created by default. - Target: ManagementStudio field (Detail, Custom, Blueprint) - MS Field: Path or field name in ManagementStudio - Intune Field: Attribute of the Intune Device object; supports attribute transformation. |
Add Intune Devices to Blueprint | #3 Adds imported Intune devices to a Blueprint. |
Add to Blueprint | #4 Sets the root for device Blueprints. |

Mapping Rules
Additional mapping logic can be configured in this panel.

Connection Options
Configure authentication and connectivity settings for the Intune connector.
| UI Element | Description |
|---|---|
Azure Account Username | #1 Azure AD username for authentication. |
Azure Account Password | #2 Azure AD password for authentication. |
Azure App Client Secret | #3 Secret key generated during Azure App registration. |
Azure App Client Secret Expiry | #4 Expiry date for the App Client Secret. |
Use Proxy Server for Internet Access | #5 Enable to connect via a proxy server. |
Proxy Server Address (Leave Blank for auto detect) | #6 Specify proxy server address, or leave blank for automatic detection. |
Proxy Account Username | #7 Username for proxy authentication. Leave blank to use the ManagementStudio service account. |
Proxy Account Password | #8 Password for proxy authentication. Leave blank to use the ManagementStudio service account. |

Troubleshooting
Access logging, help, and data anonymisation features for diagnostics and testing.
| UI Element | Description |
|---|---|
Notes | #1 Enter information about the project environment. |
Online Help | #2 Link to the ManagementStudio knowledge base solutions article. |
Verbose Logging | #3 Enables detailed logging. Produces large log files and should only be used for troubleshooting. |
Log Headers | #4 Enables logging of all request headers for diagnostic purposes. |
Log Payload | #5 Enables logging of request payloads for troubleshooting. |
Anonymise Data | #6 Imports anonymised data with the minimum necessary fields to establish User-App-Device links. Account and device names are scrambled. |

Intune Connector Setup
To establish a connection to your Intune instance:
- Ensure an Azure App is created as per the Azure App Creation Guide.
- Fig.1#1 Navigate to
Administration → Extensions → Connectors. - Fig.1#2 Click
Add New Connector. - Fig.1#3 Select
Intune. - Enter a name for the connector and click
OK. - In the Intune Discovery panel, fill in your Fig.2#1 Azure
TenantIdand Fig.2#2App ClientId. - Scroll to the Connection Options panel, and choose either:
- Fig.3#1
Azure Account UsernameandAzure Account Password - or Fig.3#2
Azure App Client Secret.
- Fig.3#1
- Fig.4#1 Click
Save Changes. - Enable required configuration panels, configuring each as needed.
- Click
Save Changesagain. - Fig4#2 Click
Run Intune Discoveryto initiate your first sync. - When prompted, click
Continue. - After a few minutes, click Fig4#3
Reloadto view the connector Fig4#4Import Log. - To automate imports, configure scheduled runs as described in the Scheduled Tasks article.
Figure 1

Figure 2

Figure 3

Figure 4

Further Support
For additional assistance, visit the ManagementStudio Service Desk to search the knowledge base or raise a new support ticket.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article