<?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/a8941dd907d84923b442fd7940bbafc3&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/a8941dd907d84923b442fd7940bbafc3-39c1d9e7f8b45443.gif</thumbnail_url><duration>282.477178</duration><title>3. PowerPlay - Post-Deployment Steps - Environment Variables</title><description>In this video, I walk you through the process of updating environment variables for both the serval and castle environments, ensuring they are correctly tied to our ALM service principle. I cover key values such as the custom connector domain, ACB server URL, and the service orchestrator app URL, which I demonstrate how to retrieve. Additionally, I highlight the importance of the IACV Sirvorg ID and the tenant ID, both of which are crucial for our setup. Please make sure to follow along and update these variables as I’ve outlined to ensure everything functions smoothly. Let me know if you have any questions!</description></oembed>