This July release of Automate365 introduces a redesigned installation experience that makes workspace provisioning easier to follow and more closely aligned with the decisions installers actually need to make. The most visible change is the move towards a question-based flow, supported by clearer grouping of settings. The release also improves how template-controlled values are presented during installation, adds Hub Site theme inheritance for branded workspaces, and clarifies the Append and Overwrite options used when deploying Structure & Content. Together, these changes reduce the amount of interpretation required during provisioning. Installers see fewer unnecessary choices, understand more quickly which settings are fixed by the template and which can still be changed, and benefit from defaults that behave more predictably. Template creators also gain a cleaner and more powerful branding configuration experience, where Hub Site theme inheritance can be used to support consistent visual identity without repeating the same setup across every template.
A simpler, question-based installation experience
The installation wizard has been redesigned to guide users through the provisioning process using clear, question-based steps. Instead of navigating technical configuration sections, installers are now guided through a more natural decision-making flow. Related settings have also been reorganized into logical groups, making the overall experience easier to understand. Content and structure options, branding, storage, governance settings, and membership configuration are now presented where users naturally expect to find them. These changes reduce cognitive load and make the installation process faster, especially for users who are less familiar with SharePoint and Microsoft Teams terminology.
Automatic Hub Site Theme Inheritance
When provisioning a workspace associated with a Hub Site, Automate365 now automatically inherits the BindTuning theme configured for that Hub Site.
Previously, while the workspace inherited the Hub Site association, the BindTuning theme still had to be applied manually after provisioning. With this enhancement, the theme can be applied automatically as part of the provisioning process, ensuring newly created workspaces are branded from the moment they're created and eliminating the need for post-installation configuration.
Preserve and control governance settings
Automate365 now preserves governance settings from the source workspace when creating a template, making it easier to maintain organizational standards across future deployments. Settings such as Sensitivity Labels, Retention Labels, and other supported governance configurations are now automatically captured during template creation. Template creators can then choose whether each setting should be enforced during installation or made editable for installers. During provisioning, enforced settings are clearly displayed as locked, while editable settings are pre-populated with the template's default values, allowing installers to make changes only where permitted. By preserving governance settings from the source workspace and clearly distinguishing between mandatory and editable options, Automate365 provides greater transparency during installation while giving template creators more control over organizational governance.
Clearer Structure & Content deployment options
We've refined the Append and Overwrite experience for Structure & Content to better reflect how these options behave during workspace deployment. The available choices have been reorganized and clarified so installers can more easily understand whether existing structure and content will be preserved or replaced. This helps reduce confusion during deployment and ensures the selected option matches the expected outcome.
This release makes Automate365 more predictable and easier to use at the points where customers configure, govern, and deploy workspaces. The redesigned installation flow, clearer handling of template-enforced settings, improved branding configuration, Hub Site theme inheritance, and more explicit Structure & Content deployment options all help reduce ambiguity and avoid unnecessary manual decisions. In practical terms, customers can configure templates with less repetition, provision workspaces with greater confidence, and maintain more consistent outcomes across Microsoft 365.
