Insights & updates from our experts
Add MS Teams Chat Link to Person Records Using SCIM
Xurrent’s SCIM provisioning capabilities have been extended to make it possible for organizations to automatically include a link for starting a Microsoft Teams chat session in each Xurrent person record.
Using SCIM, it is possible to add the following attribute to each SCIM user record in Xurrent (where users=user@example.com is replaced with each person’s actual email address):
“ims”:[{“type”:”teams”,”value”:”msteams:/l/chat/0/0/users=user@example.com”}]
Having this attribute available in each SCIM user record, allows it to be picked up by the SCIM user automation rules. The following expression can then be added to the SCIM user automation rules:

In turn, this expression can then be used in the same automation rule to define an action that adds the Microsoft Teams chat link to each Xurrent person record:

Note that the first part of the value is used to identify the protocol (telephone, email, chat or website) for the information that is to be added to the ‘Contacts Details’ section of a person record.
- email: – Xurrent protocol is set to email
- http: or https: – Xurrent protocol is set to website
- msteams: – Xurrent protocol is set to chat
- slack: – Xurrent protocol is set to chat
- skype: – Xurrent protocol is set to telephone
- everything else – Xurrent protocol is set to telephone

Having a link available in each person record to quickly start an MS Teams chat session with a colleague can be very useful, especially when specialists want to ask each other a quick question.

A Note From the Road: What SPARK Taught Me About Time
During the second SPARK event in Antwerp, I stood at the back of a training room and watched a customer build a custom integration with our new iPaaS, wiring Xurrent to another system in her stack that had never talked to it before. No services rep doing it for her. No statement of work, no project plan with a kickoff and a go-live date. Just a person with live beta access in her hands, connecting two systems by hand, and finishing it before her coffee went cold. A year ago that would have been a multi-week project with a budget attached. She looked up, a little surprised it had actually worked, and said something I have not stopped thinking about since. She said it just gave her her week back.

How Long Should ITSM Implementation Really Take in 2026?
Most vendors will tell you ITSM implementation takes six months to a year — but modern, configuration-first platforms have rewritten the math entirely. See what real implementations look like in 2026, and why a long rollout is now a choice, not a given.






.webp)





.webp)
.webp)














