<?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/ba5ff7bf8ef24763b5cece674ecad3d5&quot; frameborder=&quot;0&quot; width=&quot;1112&quot; height=&quot;834&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>834</height><width>1112</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>834</thumbnail_height><thumbnail_width>1112</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/ba5ff7bf8ef24763b5cece674ecad3d5-4f01b46761d31848.gif</thumbnail_url><duration>259.7091</duration><title>Troubleshooting Consent Loading Issues in Microsoft Integration 🔧</title><description>In this video, I explored an issue with editing consents related to user profiles, specifically focusing on how URL normalization by Microsoft might be affecting our ability to load consent data. I demonstrated creating a new user, Jane, and highlighted that the lowercase transformation of user names is causing problems in accessing consent information. Additionally, I noted that if there&apos;s a space in the user name, it alters the format further complicating the retrieval of consents. I believe this is a trivial fix that the team can implement by adjusting the logic for loading user data from the URL. I encourage the team to review this issue and consider making the necessary changes to improve functionality.</description></oembed>