<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/9f939e1f38de448688bab9d4214719b0&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/9f939e1f38de448688bab9d4214719b0-42254dd8b78808d5.gif</thumbnail_url><duration>86.666667</duration><title>2. Problem Management - Post-Deployment - Connection References</title><description>In this video, I walk you through the final steps for setting up our problem management solution by completing the necessary connection references. We need to establish four connections: one for Microsoft Teams, one for the Distractor, one for the Microsoft Dataverse, and one for the Distractor Custom Connector. I will be using a pre-existing district connection and a custom connector to streamline this process. If you haven&apos;t set up these connectors yet, please refer to the supporting documentation provided. Your prompt action on this will ensure the solution is successful.</description></oembed>