Keep an existing TOPdesk-Intune import where it fits.
More about this integration
Keep an existing TOPdesk-Intune import where it fits. Service Automation Suite connects devices and users to HR changes, handover, access and returns. MDM firewall status can also provide process context where available. Define the source per field, follow up discrepancies and verify outcomes. Capabilities depend on Graph functions, permissions and configuration.
Scenarios in practice
What would you like to do with Microsoft Intune?
Choose a use case and explore the related workflow steps.
Connect inventory from Microsoft Intune to TOPdesk Asset Management. Service Automation Suite matches devices and relationships, maps attributes and keeps agreed records current.
Service Automation Suite · Central coordination
Matching, field mapping & relationships
Add a central register and source-of-truth rules. Check differences, request missing data and determine what gets updated.
Use available device attributes and the agreed scope. Define the authoritative source for each field.
Match and update
Avoid duplicate assets, update changed fields and connect the right people to their assets.
Connect records to follow-up
Connect missing data, a changed owner or an employee departure to tasks, changes or asset returns.
Onboarding
From employee change to a complete start.
Service Automation Suite connects IAM to the wider employee workflow. Use a matrix in Service Automation Suite to relate roles to access, assets and tasks, for example. Combine those rules with current HR and TOPdesk data and agree who maintains the matrix. This determines the changes and actions needed.
Service Automation Suite · Central coordination
Lifecycle matrix, form & exceptions
Combine the data with your policy, risk assessments and checks. Request information or a decision where needed, track actions and record the outcome.
Use the HR change and current person, access and asset data. Forms or reviews supply missing information and exceptions.
Let the matrix define the route
Service Automation Suite applies role profiles, conditions and effective dates. Start or update the TOPdesk change with appropriate activities for HR, IT and facilities.
Execute, confirm and update
Connect account and group actions to asset handover and confirmation. Include ValidSign signing and file storage where needed. Return outcomes to the activities.
Complete the loop with HR
Once the account is created, write agreed account data or status back to AFAS or the chosen HR source. The TOPdesk activity receives the same outcome. HR and IT no longer need to copy or chase confirmation separately.
View the complete employee lifecycle
Offboarding
Departure known. Access and assets follow through.
Service Automation Suite connects IAM to the wider employee workflow. Use a matrix in Service Automation Suite to relate roles to access, assets and tasks, for example. Combine those rules with current HR and TOPdesk data and agree who maintains the matrix. This determines the changes and actions needed.
Service Automation Suite · Central coordination
Lifecycle matrix, form & exceptions
Combine the data with your policy, risk assessments and checks. Request information or a decision where needed, track actions and record the outcome.
Use the HR change and current person, access and asset data. Forms or reviews supply missing information and exceptions.
Let the matrix define the route
Service Automation Suite applies role profiles, conditions and effective dates. Start or update the TOPdesk change with appropriate activities for HR, IT and facilities.
Revoke, recover and complete
Connect revocation of access and groups to asset returns. Update relationships and records, keeping open activities visible until their outcome is known.
Complete the loop with HR
Return confirmed changes or revocations to TOPdesk activities and, where agreed, the HR source. Employee records, execution and follow-up stay aligned.
Handover & return
Every asset has an owner. Even after a change.
Connect devices and records to the employee and the actual handover. A missing device is not automatically a returned laptop.
Service Automation Suite · Central coordination
Combine data and apply rules
Combine the data with your policy, risk assessments and checks. Request information or a decision where needed, track actions and record the outcome.
Link the correct person to the asset and remove outdated relationships on reassignment or return. HR and other sources can provide the necessary context.
Coordinate handover or return
Have the responsible person confirm the handover and update agreed relationships.
Keep open actions visible
Follow up missing returns and outdated relationships on reassignment or departure.
Alerts & follow-up
Give every discrepancy an owner.
Turn a relevant status or discrepancy into actionable work. Add context and route follow-up to the right team.
Service Automation Suite · Central coordination
Combine data and apply rules
Combine the data with your policy, risk assessments and checks. Request information or a decision where needed, track actions and record the outcome.
Read available MDM device data, including firewall status, through the configured Intune/Graph capabilities. Service Automation Suite makes the status available in process context; this does not mean Service Automation Suite changes the firewall setting.
Add context and routing
Connect customer, device or service context where available. Apply your priority and ownership rules.
Track resolution
Create or update a ticket and keep execution and feedback in the same process.
Coordinate actions
Turn a decision into completed work.
Connect a request or discrepancy to a workable process. Let people decide where needed and systems execute the agreed actions.
Service Automation Suite · Central coordination
Combine data and apply rules
Combine the data with your policy, risk assessments and checks. Request information or a decision where needed, track actions and record the outcome.
Choose the request, change or discrepancy that needs follow-up and who decides.
Coordinate TOPdesk changes and activities
Let changes or discrepancies create or update agreed changes and activities. Connect approval, execution and feedback to the same record; configure the route around your process and system capabilities.
Record the result
Record which steps are complete and where someone still needs to act.
Assets & CMDB sync Popular
From Microsoft Intune to an up-to-date CMDB.
Read available data from Microsoft Intune and connect it to TOPdesk Asset Management or Matrix42, for example. API Composer configures retrieval and writes. DataFlow Composer prepares the right selection, field values and relationships for the CMDB.
Service Automation Suite · Central coordination
API Composer · DataFlow Composer
Add a central register and source-of-truth rules. Check differences, request missing data and determine what gets updated.
For Microsoft Intune, assess device ID, serial number, available user and management attributes. Define reliable matching, for example a source ID plus customer or tenant, or a serial number. A computer name alone is not always unique.
Read, combine and map
API Composer retrieves permitted data through the selected API. DataFlow Composer filters and normalises values, compares existing records and relates customer, location and person references where available. Where paginated, retrieve the complete agreed selection.
Create, update and verify
Create a missing asset or CI, or update agreed fields through the destination API. Retain source and destination IDs and check the response. Route uncertain matches for review; missing telemetry does not automatically mean deletion.
We choose data, direction and frequency based on available interfaces, modules and permissions. An existing import can remain in place; only agreed fields are updated.
Connect tickets with CC
Keep the alert and its resolution connected.
Follow up a relevant alert or discrepancy from Microsoft Intune in TOPdesk, Matrix42 or another service tool, for example. Collaboration Composer (CC) handles ticket collaboration; API Composer and DataFlow Composer can add device, customer and CMDB context.
Service Automation Suite · Central coordination
Collaboration Composer (CC)
Combine the data with your policy, risk assessments and checks. Request information or a decision where needed, track actions and record the outcome.
Select relevant alerts or requests. Match the same source event before creating another ticket; add the correct asset, customer and service where available. An update is not automatically a new incident.
Connect tickets and working agreements
Use CC to configure which fields, comments and statuses are exchanged. Retain both ticket references and agree priority, ownership and resolution. Share internal notes and attachments only when explicitly agreed and supported.
Record confirmed progress
Return the agreed outcome and route failures for retry or review. A cleared monitoring alert does not automatically close an incident or security investigation. Configure writes back to Microsoft Intune only for demonstrably supported actions; otherwise retain a reference to the service ticket.
Check discrepancies Popular
Discovered, recorded and in use: do they still match?
Compare available operational data with agreed CMDB records. DataFlow Composer makes missing, duplicate or inconsistent data actionable. Define the source per field; not everything needs two-way synchronisation.
Service Automation Suite · Central coordination
DataFlow Composer · API Composer
Add a central register and source-of-truth rules. Check differences, request missing data and determine what gets updated.
Agree ownership of serial number, location, user and lifecycle state, where available. Consider measurement time and source quality. A missing device is not the same as a confirmed return.
Correct only what is agreed
DataFlow Composer compares data and prepares the appropriate change. API Composer writes only permitted fields after agreed checks. Conflicting or uncertain matches remain assigned for review.
Connect exceptions to work
Let a relevant discrepancy start a ticket or task in your service workflow, using CC where needed. Retain comparison results, references and outcomes so the next run can be checked and repeat alerts reduced.
How Service Automation Suite connects data and execution
The work between your applications
Records updated. Do they match reality?
Service Automation Suite connects Microsoft Intune with your other applications, people and rules. Keep data aligned, work moving and outstanding actions visible.
A change, request or alert
Service Automation Suite
Data, people, assets and relationships on one foundation.
Compare
What exists? What should exist?
Determine what is needed
Matrix · policy · legal requirements
Coordinate the next steps
Checks · tasks · approvals · actions
Execution ↔ feedback
Your people and tools
Microsoft Intune
For example. Also with other teams, suppliers and applications.
Verify. Inform. Report.
What is complete? Who needs to act? Which exception needs attention?
Start with one integration, register or check. Build on the same data and rules.
Combine into one controlled process
Data → rules → execution
Combine
Inventory + CMDB + ownership
Determine & check
Match, compare and review discrepancies
Execute & report back
Update CMDB · Create service ticket · Review replacement or retirement
Check sources and rules, test changes and track the outcome. Manual tasks get an owner and confirmation.
Build visually. Manage easily.
Reuse building blocks, adapt your process and test the change. Manage it yourself, together with us or let Scope4mation take care of it.
From product to process
How to use the integration
Assets → CMDB
Synchronise agreed device fields with your CMDB, for example TOPdesk or ServiceNow.
Device → person
Relate devices to the agreed person record and update the relationship on reassignment.
IT asset lifecycle
Compare inventory with operational records and initiate checks for reassignment, replacement or retirement.
Connect work across your applications
What would you like to connect Microsoft Intune with?
Choose the role in your workflow. Explore applications from the scenarios and further directions to discuss together. We define the data, actions and available interface for each combination.
Connect Microsoft Intune with your other applications. Automate the work between them and stay in control.
Process & control
Less manual work
Connect Microsoft Intune with HR, IT and suppliers. Automate the flow of data and actions.
Control over execution
Define rules, follow up exceptions and verify the outcome.
Purposeful data sharing
Decide which data to share, with whom and under which conditions.
Autonomy & choice
Your applications, one process
Combine Microsoft Intune with the applications that fit your organisation.
Direct access to the makers
Work directly with Scope4mation: Dutch technology, process expertise and support in one team.
Room to adapt
Reuse your configuration and keep process knowledge transferable as systems or rules change.
Build & operate together
Start small, build further
Start with one use case and reuse the building blocks for the next.
From idea to practice, together
We help with configuration, exceptions and handover, starting from your daily practice.
Operate it your way
Operate it yourself, together or with us. Agree on clear responsibilities upfront.
Under the hood
This integration, step by step.
How we configure this example
Keep Intune devices identifiable in your asset records
Connect and retrieve
Use the existing TOPdesk Intune import when it already provides inventory. Retrieve additional device context through Microsoft Graph only where needed.
Find the correct record
Store the managedDevice ID alongside the serial number and Entra device reference. This distinguishes a new enrolment from the physical device.
Execute the agreed action
Link device and user references to the HR change or handover/return request. Update agreed additional fields only and retain the existing import as the inventory source.
Verify the outcome
Verify the target record and handle stale inventory separately. A 403 requires a permissions check; a 429 requires waiting according to the API response. Retire and wipe do not belong in inventory synchronisation.
Start with one use case. Connect customer, employee and asset data, for example, and agree which source is authoritative. Reuse those relationships, a matrix where needed and configured actions in the next workflow. Agree who maintains the data and rules. Expand without repeatedly connecting and maintaining the same information.
A replacement laptop without losing context.
An employee receives a replacement device. The old asset, new record and open service or security tickets must remain connected.
Combine
Use the central relationship between owner and device identifiers. Combine handover, technical inventory and return with existing tickets.
The outcome determines what follows
Receipt confirmed: update ownership and relationships. Old device missing or uncertain match: start a targeted review instead of overwriting historical records.
The benefit
Current records and a traceable handover even when a management tool uses different names.
A different name does not mean a new record.
A person or organisation has a different name in the source than at a customer or supplier. Matching text again can create incorrect or duplicate relationships.
Combine
Retain verified identifiers and source rules in a shared table. Reuse the relationship for requests, tickets and other integrations.
The outcome determines what follows
Known key: use the relationship. Multiple candidates or a missing identifier: request review. Once confirmed, reuse the established relationship.
The benefit
A consistent data foundation managed by your team instead of investigated again for every connection.
Ordered, delivered and actually in use?
Procurement, a supplier and technical inventory each hold part of the picture. A delivered asset is not automatically assigned to its correct owner.
Combine
Compare orders, delivery details, serial numbers and inventory with central ownership relationships. Keep missing confirmations part of the workflow.
The outcome determines what follows
Matching data: update the agreed records. Unknown device, unexpected owner or unconfirmed delivery: create work for the correct support group.
The benefit
Fewer gaps between administrative and technical records and targeted follow-up of discrepancies.
Your process needs more than a standard action?
Configure the missing API request, input and output in API Composer. Use its response in the next step and combine it with data tables, forms and automations. Extend the same product and reuse the configured building blocks.
Use Service Automation Suite to update a ticket in TOPdesk, for example, with fields available through its API, such as category, priority, status and support group. For another application, configure its request and field mapping. The outcome determines the next action: confirm, add information or request review, not merely check whether the request arrived.
Need to publish data or let others submit it? Endpoint Composer exposes a configured Service Automation Suite data object with selected methods and security profiles. Other building blocks handle subsequent processing.
From product to workflow
Microsoft Intune in your workflow
Part of one workflow
From delivery to current asset records
Supplier data creates the initial record. Then compare with Intune, for example, and update TOPdesk selectively according to your source rules. Follow up exceptions and verify confirmed outcomes again.
