Each time we create a team from a template, Microsoft associates a SharePoint site to it to store this team’s content. Ok, you might already know that.  And suppose you’re used to Teams provisioning with ShareGate. In that case, you also know that whenever users created teams from the templates you provided, with your policies and guardrails in place, they were associated with generic, default SharePoint sites. Blueprints came to transform that.  With ShareGate Blueprints, you identify an existing SharePoint site that fits the purpose of your Teams template and embed it in your provisioning templates. So, when someone provisions a team with that template, ShareGate’s powerful migration engine copies the blueprint site with all its content, folders, web parts, and components. This way, end users can create perfectly purpose-fit Teams sites just minutes after the workspace’s creation, while IT ensures the new content will be fully secure and compliant with their policies.  A good part of the ShareGate Blueprints magic comes from our dynamic templates. With them, any changes you apply to the blueprint site will dynamically show in the provisioning template, ensuring it will be updated the next time employees use it to create a team and making it much easier for IT to maintain their templates.