<?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/257425f8839a4981aeb9e6e04a8812e2&quot; frameborder=&quot;0&quot; width=&quot;3840&quot; height=&quot;2880&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>2880</height><width>3840</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>2880</thumbnail_height><thumbnail_width>3840</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/257425f8839a4981aeb9e6e04a8812e2-00001.gif</thumbnail_url><duration>90.78000000000002</duration><title>Orchestry New Feature : Archival of Groupless Workspaces</title><description>Hi there! In this video, I&apos;ll be showing you how to handle SharePoint sites that have been left behind due to a removed group. I&apos;ll explain how Orchestry excludes these objects from archival and how you can now untoggle the automated change and force a policy to be applied. I&apos;ll also demonstrate what happens when you try to delete a workspace and how we can log the unsuccessful deletion. Finally, I&apos;ll show you how this new feature allows you to move workspaces out of the limbo state and into an archive status, even if the retention is still in place. So, let&apos;s get started!</description></oembed>