<?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/2432eb72bae0449b80efe30b01fee08f&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/2432eb72bae0449b80efe30b01fee08f-03f702dc98ef620b.gif</thumbnail_url><duration>151.564</duration><title>Updates to Connect to Forge Tool for Data Residency</title><description>In this video, I demonstrate the recent changes we&apos;ve made to our Connect to Forge tool to enhance support for data residency in Forge remotes. We updated the tool to accommodate new manifest schemas, which now include region-based URLs for the US and EU. I walk through the conversion process of a test app, highlighting key features like the data migration webhook and the operations involved. Please take a look and let me know if you have any questions or need further clarification on the changes.</description></oembed>