Stop rebuilding the same site by hand. Copy its structure to the next one in minutes.
DeployPoint runs on the site owner's own connections, so no tenant-wide app consent and no elevated role is required to run a provisioning. One boundary, said plainly: DeployPoint moves site structure today, not documents or list items.
Bauer Automate is a Microsoft 365 and Power Platform consultancy in Calgary, Alberta, Canada. DeployPoint is the deployment engine we use to provision SharePoint sites from a template in your own tenant: it reads a source site's structure, a consultant reviews and adjusts it, and a flow deploys it to the target site. You get it inside ProjectPoint or through a Bauer Automate engagement; it is not sold on its own.
Book a free consultationSee what it moves today
Three routes
There is nothing to buy separately. DeployPoint arrives inside a product or an engagement.
Best for: A firm that wants one consistent SharePoint site for every client or project.
Best for: An IT team or site owner with a site worth cloning and a list of sites to clone it to.
Best for: A firm starting with time off requests in its own Microsoft 365.
Structure, exactly
Everything in this table is read from the source site and recreated on the target. Nothing outside it is promised.
| Site structure | Copied today |
|---|---|
| Site columns, including lookups, calculated columns and validation formulas | ✓ |
| Site content types, and the content types attached to each list | ✓ |
| Lists and document libraries, with their columns | ✓ |
| List views, with their columns, sort and filter | ✓ |
| Column and view formatting (the JSON that colours a status or draws a bar) | ✓ |
| Site and web features | ✓ |
| Quick launch (left-hand) navigation | ✓ |
| A readable build definition and an Excel log of every step, kept per run | ✓ |
Two things worth knowing before a demo. A run is a sequence of steps, so a run that stops partway is picked up and finished by a person rather than rolled back on its own. And naming conventions and sensitivity labels stay with your standard tenant governance rather than being stamped by the engine at the moment of creation.
Three steps
Capture once, review as often as you like, deploy to as many sites as you need.
A flow reads the source site and writes its structure to a file: columns, content types, lists, libraries, views, formatting, features and navigation.
A consultant opens that file with you. Columns get renamed, clutter gets dropped, missing pieces get added, and every rename carries through to the formulas, formatting and views that depend on it. The result is checked against the source before anything deploys.
A flow applies the reviewed structure to the target site using the site owner's own connection, one step at a time, and logs each step to an Excel workbook you keep.
The permission model
DeployPoint runs on Power Automate connections owned by the site owner who installs it, calling SharePoint for actions that owner already has the right to perform. No tenant-wide application is consented into your directory, and no elevated role is required to run a provisioning. That is a deliberately precise claim: it is about the provisioning run, not about your whole tenant.
Whether people can create SharePoint sites at all is one tenant-wide setting your IT team already controls. If they have turned it off, a site owner cannot create the target site no matter how the tool signs in, and that is as it should be. DeployPoint works inside that decision, not around it. We ask for the roles a task needs and never Global Administrator, and we remove our own access when the job is done.
Coming next
These are in development and are not part of any DeployPoint run today: copying documents and list items between sites; copying site pages and their web parts; list and library settings such as versioning and check-out; calendar, board and gallery views; site theme and branding; and self-serve deployment of PeoplePoint through the engine. The product roadmap shows what is in development and what is available now.
Before you book
Five questions IT teams ask before they approve it.
DeployPoint is the deployment engine Bauer Automate uses to provision SharePoint sites from a template in your own tenant. It reads a source site's structure, lets a consultant review and adjust it, and deploys it to a target site through a flow that runs on the site owner's own connection.
No. It arrives inside ProjectPoint, inside PeoplePoint Time Off, or as the engine behind a Bauer Automate provisioning or clean-up engagement. If you have a site worth cloning, the free consultation is where we scope that engagement.
Not to run a provisioning. The engine runs on connections owned by the site owner, so no tenant-wide app consent and no elevated role is required for the run itself. Whether users may create sites at all is a tenant setting your administrators control, and DeployPoint works inside it.
Not today. DeployPoint copies structure: columns, content types, lists, libraries, views, formatting, features and navigation. Copying documents and list items is in development and sits in the Coming next strip above.
A script is a fine choice when someone owns it. The difference is the review step and the log: a consultant checks the captured structure against the source before it deploys, every rename carries through to dependent formulas and views, and each run leaves an Excel record of what it did. If your team already maintains scripts that do this, we will say so in the consultation.
Book a free consultation and bring the site. We will show you what a capture of it looks like.
We acknowledge that we live and work on Treaty 7 Territory and across Alberta, honouring the traditional lands of the Blackfoot Confederacy, Tsuut’ina Nation, Îyâxe Nakoda Nations, and the Métis Nation of Alberta, and remain committed to respectful relationships with Indigenous Peoples wherever we operate. Learn more about Bauer Automate's commitment to Reconciliation.
We are dedicated to building an inclusive technology community. We champion diversity, equity, and opportunity so people of all backgrounds, identities, and experiences can collaborate, innovate, and thrive. Learn more about Bauer Automate's commitment to Inclusivity.
All rights reserved Bauer Automate Inc. ©2022-2026