Bauer Automate - Blog Posts #SharePoint

5 Business Processes That Are Still Shockingly Manual (and Easy to Automate)

Wed, 11 Feb 2026 09:03:41 -0700

Despite years of digital transformation, many organizations still rely on manual business processes to run critical operations. Email/folder-based approvals, spreadsheet-driven reporting, and repetitive data entry remain common — even though business process automation tools are widely available.

These manual workflows don’t just slow teams down. They increase errors, reduce visibility, and prevent organizations from scaling efficiently.

The good news is that many of these processes are ideal candidates for workflow automation using modern low-code automation platforms.

Below are five manual business processes that are still shockingly common — and easy to automate.

1. Approval Workflow Automation (Time Off, Purchases, Expenses)

Approval workflows are one of the most common examples of manual business processes. Time-off requests, purchase approvals, and expense sign-offs are often handled through long email threads with no visibility or audit trail.

High-Level Approval Automation Example

Request Intake: Microsoft Forms or Power Apps
Data Storage: SharePoint list
Workflow Automation: Power Automate routes approvals based on rules
Notifications: Email and Microsoft Teams
Tracking: Centralized approval status and history

This type of approval workflow automation replaces inbox chaos with a structured, trackable process.

Estimated Setup Time: 4-8 hours (basic approval workflow), or 8-12 hours (multi-level workflow automation)

Typical Time Saved: ~10-15 minutes per request | ≈ 40-60 hours saved per year

2. Repetitive Data Entry and System-to-System Automation

Manual data entry across systems is one of the biggest drains on productivity. Teams often copy the same data into spreadsheets, CRMs, accounting systems, or internal tools.

High-Level Data Entry Automation Example

Single Data Capture: Form or Power App
Primary Data Store: SharePoint or Dataverse
Workflow Automation: Power Automate syncs data across systems
Validation Rules: Reduce errors and rework

By automating this business workflow, organizations eliminate duplicate work and improve data accuracy.

Estimated Setup Time: 6-12 hours

Typical Time Saved: 3-5 minutes per entry | ≈ 60-100 hours saved per year

3. Document Automation and File Management

Many organizations still rely on manual document creation for proposals, contracts, letters, and internal documentation. These manual workflows often lead to inconsistent formats and version control issues.

High-Level Document Automation Example:

Data Input: Power App or Form
Document Automation: Generate Word or PDF files from templates
File Management: Store documents automatically in SharePoint
Notifications: Automated sharing and alerts

This form of document automation ensures consistency while reducing manual effort.

Estimated Setup Time: 6-12 hours

Typical Time Saved: 10-20 minutes per document | ≈ 85-170 hours saved per year

4. Automated Reporting and Workflow Automation

Reporting is still one of the most manual business processes in many organizations. Data is exported, cleaned, and reassembled in spreadsheets before being shared with stakeholders.

High-Level Automated Reporting Example

Data Sources: SharePoint, Dataverse, or line-of-business systems
Workflow Automation: Scheduled data refresh via Power Automate
Reporting: Power BI dashboards with automated updates
Distribution: Automated report sharing

This approach to automated reporting ensures leaders always have access to up-to-date information.

Estimated Setup Time: 8-16 hours

Typical Time Saved: 2-5 hours per reporting cycle | ≈ 25-60 hours saved per year

5. Business Process Automation for Onboarding

Employee and vendor onboarding often spans multiple departments and systems, making it one of the most fragmented manual workflows in an organization.

High-Level Onboarding Automation Example

Intake: Onboarding Form or Power App
Workflow Automation: Automated task assignment and reminders
Tracking: Central SharePoint list or app
Communication: Automated status updates

This type of business process automation improves consistency while reducing onboarding time.

Estimated Setup Time: 8-14 hours

Typical Time Saved: 1-2 hours per onboarding | ≈ 25-50 hours saved per year

Ready to Automate the Work That Slows Your Team Down?

Learn how Bauer Automate helps organizations replace manual business processes with secure, scalable workflow automation using Microsoft Power Platform.

Whether you’re looking to automate approvals, reporting, document management, or system integrations, we focus on practical automation that delivers real ROI — fast.

Book a FREE Automation Discovery Call

From Manual to Automated: Where Microsoft's Power Platform Delivers the Biggest ROI

Thu, 08 Jan 2026 09:16:51 -0700

Most organizations don’t struggle because they lack software — they struggle because too much work still happens manually.

Emails are forwarded. Spreadsheets are copied. Approvals are chased. Data is re-entered across systems. These small inefficiencies compound quickly, costing time, money, and focus.

This is where Microsoft Power Platform consistently delivers one of the strongest returns on investment we see with clients.

Not because it replaces people — but because its workflow automation tools removes insignificant manual repetitive tasks, allowing your team to focus on what truly matters. Plus, it is already included with a Microsoft 365 subscription, so no extra subscriptions are required!

Why Manual Processes Quietly Kill ROI

Manual workflows often feel “good enough” until you step back and measure them:

Time lost to repetitive data entry
Errors caused by copy-paste or version confusion
Delays from approval bottlenecks
Lack of visibility into who owns what and when

The real cost isn’t just hours — it’s decision latency, burnout, and missed opportunities.

Automation of manual processes fixes this by making work predictable, auditable, and fast.

The 5 Areas Where Power Platform Delivers the Biggest ROI

1. Request & Approval Workflows

Nearly every business runs on requests:

Time off
Purchase approvals
Policy exceptions
Access requests
Vendor onboarding

When these live in email, the process breaks down fast.

Power Automate + Power Apps turn these into structured workflows with:

Clear ownership
Automated routing
Real-time status visibility
Audit history

ROI impact: Faster cycle times, fewer follow-ups, less admin overhead.

2. Data Collection & Validation

Forms filled out incorrectly create downstream rework.

With Power Apps and Microsoft Forms, organizations can:

Enforce required fields
Validate data at entry
Standardize inputs across teams
Write directly to SharePoint or Dataverse

This removes cleanup work before it even starts.

ROI impact: Fewer errors, higher data quality, cleaner reporting.

3. Reporting & Decision Visibility

Manual reporting usually means:

Exporting spreadsheets
Manual report creation
Reconciling numbers
Questioning accuracy

Power BI connects directly to live data sources, giving leaders:

Real-time dashboards
Automated refreshes
Single source of truth

No more chasing numbers — just decisions.

ROI impact: Faster insights, less analyst time, better decisions.

4. Document Management & Metadata Automation

Documents are expensive when they’re misfiled, duplicated, or lost.

With SharePoint + Power Automate (and a sprinkle of AI), teams can:

Auto-tag documents with metadata
Route files to the right libraries
Enforce naming standards
Apply security by destination

ROI impact: Reduced search time, improved compliance, lower risk.

5. System Integration Without Custom Code

Many organizations rely on disconnected tools:

Accounting systems
CRMs
Line-of-business apps
Power Platform automation acts as the glue:
Sync data automatically
Trigger actions across systems
Reduce duplicate entry

And it does this without long custom development cycles.

ROI impact: Lower integration costs, faster deployments, scalable automation.

Why Power Platform ROI Is So Strong

The platform delivers ROI quickly because:

It builds on workflow automation tools organizations already license (Microsoft 365)
It supports incremental automation (start small, scale fast)
It empowers both IT and business users
It reduces dependency on custom code

You don’t need a massive transformation to see value — just the right workflows automated first.

Final Thought

Automating manual processes isn’t about replacing human work.

It’s about removing the parts of work humans shouldn’t be doing.

When manual processes are replaced with structured, automated workflows, teams move faster, make better decisions, and focus on higher-value work.

That’s where Microsoft Power Platform consistently delivers the biggest ROI.

Ready to Automate the Work That Slows Your Team Down?

Learn how Bauer Automate helps organizations identify high-impact manual processes and replace them with secure, scalable automation using Microsoft Power Platform.

Whether it’s approvals, reporting, document management, or system integrations, we focus on practical automation that delivers real ROI — fast.

Book a FREE Automation Discovery Call

Two Years of Reflection at the CPPUG — And Why 2026 Has Us Excited

Wed, 03 Dec 2025 11:59:32 -0700

When we look back at the last two years of running the Calgary Power Platform User Group (CPPUG), it still feels a bit surreal. This group didn’t start with us — we had the privilege of taking it over at a time when things were quiet and activity had slowed.

What began as an opportunity to revive something meaningful quickly turned into a mission: to rebuild the CPPUG into a space that truly brings Power Platform enthusiasts in Calgary together — not just for events, but as a real resource for learning, support, and community. Office Hours became a core part of that vision, giving people a place to ask questions, learn from each other, and grow together.

Today, CPPUG feels louder, fuller, and more alive than ever.

We’ve seen new faces turn into familiar ones. We’ve watched Office Hours grow from small, question-driven sessions into packed, high-energy discussions. And month after month, the room reminds us why this community matters.

A Community That Just Keeps Showing Up

A Big Milestone: The Power Platform Conference

One of our favourite moments this year was attending the Power Platform Community Conference in Las Vegas and representing the CPPUG on a global stage! Being able to share the story of our group — how we stepped in to rebuild it, how Calgary’s community is thriving, and how we intentionally make learning fun — was a powerful and proud moment.

And then came one of those “small world” experiences we’ll never forget.

One of our CPPUG stickers made its way all the way to Mexico — through someone Ryley had worked on a past project with. A member of his company attended the conference, brought stickers back for the team… and that old colleague messaged Ryley saying, “I just got a Calgary Power Platform User Group sticker.”

From Calgary to Vegas to Mexico — unreal.

P.S. If you want to watch our presentation at the Power Platform Conference, you can view it here:

Watch Our PPCC 2025 Presentation

Looking Ahead to 2026

If the last two years were about rebuilding and momentum, 2026 is all about expansion and elevation.

We’re planning:

Bigger, more dynamic events
New training and learning opportunities
Stronger partnerships behind the scenes
And brand new experiences… including our first hackathon that everyone’s been waiting for 😉

We want to make the CPPUG even more accessible — more hands-on, more welcoming, and more representative of everyone shaping the Power Platform space in Calgary and beyond.

Expect:

More Office Hours
More networking
More community highlights
More fun
And definitely more photos — because our group pictures are basically tradition now

A Huge Thank You

Running this group takes time, behind-the-scenes planning, and a lot of heart — and we wouldn’t trade any of it. Thank you to everyone who has attended, volunteered, presented, shared posts, or supported us from afar. You are the reason this group continues to grow.

2024 and 2025 were transformational.

2026 is going to be unforgettable.

— The CPPUG Team

Calgary Power Platform User Group

Want to Be A Part of the CPPUG Team?

Learn About CPPUG

View Our Event photos

Automating Microsoft Teams Memberships with Power Automate & Graph API: One Nite Band Workflow

Thu, 31 Jul 2025 17:23:56 -0600

How We Streamlined Musician Scheduling Using Power Platform & Microsoft Graph

Introduction: From Simple to Sophisticated

This post is a collaboration between Ryley Bauer and Thanishque Harshaa.

What started as a straightforward project quickly evolved into a layered, enterprise-grade automation system.

A local band—One Nite Band—needed a smarter way to manage incoming show requests and musician availability. Their goal? Replace a messy, manual process with a scalable, repeatable solution using Microsoft Teams, Power Automate, SharePoint, and the Microsoft Graph API.

Core Challenge:

Track incoming event bookings
Invite the right musicians to “bid” for availability based on their based on role and priority
Automatically assign accepted musicians to a collaboration space

What started as a “weekend Power Automate flow” turned into a deep dive into identity resolution, schema enforcement, and navigating the nuanced constraints of Microsoft Teams and Azure Active Directory. While the use case was built for musicians, the architecture applies to any project requiring dynamic team assembly—whether it’s teams of developers, analysts, designers, technicians, consultants, creatives, etc.

Project Goal: Automate Smart Role-Based Channel Assignment in Microsoft Teams

The key objective was to automate how internal and external musicians (like drummers, vocalists, and guitarists) were added to their respective Teams channels based on:

Priority: Invitations were sent based on a role-specific hierarchy
Relevance: Only the required roles for the event were contacted
Automation: Accepted musicians were granted channel access automatically via Teams channel membership.
Traceability: All actions were integrated with SharePoint and Power Automate for tracking.

To avoid clutter and confusion, general requests were routed through public channels, keeping private channels reserved for more specialized teams, while allowing the wider team to coordinate openly.

Key Technical Learnings and Challenges

1. Internal vs. External Users: It's Not Just a Checkbox

At first, we treated all users the same. Big mistake. Some of the issues we ran into include:

External users contain #EXT# in their userPrincipalName, a reliable pattern we used to differentiate them.
You can’t assign external users as owners in private Teams channels as this throws an instant Graph API error
You can’t reference external users in Graph API until they’ve accepted an Azure AD invitation

Solution: We added conditional logic to gracefully handle the onboarding of external members, avoiding hard errors and flow failures.

Takeaway: External users require manual onboarding or invitation acceptance before you can automate their involvement.

2. Why concat() Almost Broke the Flow

An early approach we used was by using concat()) to build JSON payloads dynamically.

That however, did not age well.

Even one null value (like a missing user ID) would break the entire concat() chain, causing the flow to fail with hard-to-trace errors.

Solution:

Use array variables to build each member object
Wrap dynamic fields with guards: if(empty(...), '', ...)
Debug payloads one object at a time

3. User GUIDs Are Mandatory for Graph API

The Graph API requires GUIDs, not usernames or emails.

The user@odata.bind value must be:

"user@odata.bind": "https://graph.microsoft.com/v1.0/users/{userId}"

…in which the userid must be the GUID which was retried using the Get User Profile (V2) in Office 365 actions.

*Note: If this step was skipped, the member addition will have failed silently or throw vague schema errors.

4. Schema Errors & Permission Pitfalls

The Graph API is unforgiving. Common issues included:

“Property members in payload has a value that does not match schema”
“Guest users cannot be added as owner”

Solution:

Validate user type before assigning owner/member roles
Keep the templates for owner/member schema separate
Only add accepted external users

5. Array Variables: Your Flow’s Best Friend

Switching to array variables was a huge turning point for our project.

Instead of stitching strings together, we appended validated user objects into a clean array and passed that to the HTTP request. This gave us control, modularity, and fault tolerance. Our robust member arrays instead looked like this:

{

"values": [

{

"@odata.type": "#microsoft.graph.aadUserConversationMember",

"roles": ["member"],

"user@odata.bind": "https://graph.microsoft.com/v1.0/users/{userId}"

}

]

}

Result: This made testing and debugging seamless, as we could preview each object before sending, as well as add failover logic easily.

6. Unexpected Microsoft Teams Constraints

Even with flawless logic, one of the unexpected hurdles we hit came from the Microsoft Teams limitations, which include:

Only 30 private channels per team
Certain roles can’t be added as owners
Graph API schema is rigid—any deviation causes full rejection

Although these were not power Automate issues, they were platform constraints by Microsoft Teams that required careful workaround via trial and error.

Real-World Impact: From Jam Nights to Project Teams

This automation now powers real-time musician scheduling for a rotating band roster—ensuring the right people get contacted, and the right channels stay clean and efficient.

But this system also models a powerful project resourcing tool beyond. We built a Project Management platform where roles (e.g., dev, QA, designer) are mapped, priority candidates are invited first, and project workspaces are created dynamically with full support for internal and external collaborators.

With a few tweaks, this could be a full-fledged project resourcing engine for any Microsoft 365 environment.

Final Thoughts: Beyond the Flow

This wasn’t just a flow—it was an education.

It taught me about:

Microsoft identity models
Power Platform resiliency
Real-world system design with API constraints

On some days, it felt like duct-taping XML to JSON. Other days, everything clicked, and the system worked beautifully.

What started as a simple ask—“Can you assign musicians to Teams?”—became a milestone in my journey as a Power Platform developer. It deepened my API knowledge, strengthened my problem-solving under pressure skills, and gave me hands-on skills that I’ll carry into every project moving forward.

Want to Learn More or Set Up A System that Works for You?

Using Power Automate to Create a Photo Library and Add it to the Navigation

Sat, 01 Apr 2023 22:07:46 -0600

Adding a photo library programmatically

One of our clients came to us with a request for creating a SharePoint site automatically based on a project management list. If a project was set to "Start", then a SharePoint site would be created. That will be covered in another article, but one of the interesting asks was to automatically include a photo library that would also be displayed in the QuickLaunch Navigation.

I referenced this article for the API syntax: http://www.ludovicperrichon.com/sharepoint-rest-api-call-with-powerautomate/#createlink

Create your flow however you like, a simple way to set this up is to create an instant flow and use the button trigger with a single input for the SiteURL.
Create a "Send HTTP request to SharePoint" step.

Site address: SiteURL
Method: POST
URI: _api/web/lists
Headers:

Accept | application/json;odata=verbose
Content-Type | application/json;odata=verbose

Body:

{

"__metadata":{

"type": "SP.List"

"AllowContentTypes": true,

"BaseTemplate": 109,

"ContentTypesEnabled": false,

"Description": "Photo library for __________",

"Title": "Photos"

}

Add another "HTTP to SharePoint" step

Site address: SiteURL
Method: POST
URI: _api/web/Navigation/QuickLaunch
Headers:

Accept | application/json;odata=verbose
Content-Type | application/json;odata=verbose

Body:

{

"__metadata": { "type": "SP.NavigationNode"},

"IsExternal": false,

"Title": "Photos",

"Url": "SITEURL/photos"
}

Get Started Now

Using PowerShell to Save or Clone an Existing SharePoint Online Site to Publish a the Global Template to the "From Your Organization" Menu

Sat, 14 Jan 2023 17:56:09 -0700

SharePoint Online is a powerful tool for creating intranet sites, and it's even more powerful when you can create and use custom templates to streamline the process for multiple projects or clients. Unfortunately, creating a template from an existing SharePoint Online site can be a difficult task, especially for non-programmers.

In the past, creating a template was as simple as a few clicks in SharePoint classic, but with the new SharePoint Online, it's not so easy anymore. I've tried various methods, such as using flows and http requests, but I've found that the best way to clone a site multiple times is by using PowerShell to export the existing site and create a template from it.

I created a simple script based on Microsoft's documentation, and even corrected a typo in the documentation regarding spaces in list and library names. I even corrected a typo on the docs! The internal names, such as "Shared%20Documents" had to be used instead of "Shared Documents".

In the upcoming Part 2 of this post, I will review the entire workflow, from a SharePoint list for projects, to a Power Automate flow that creates the site, provides permissions, applies the template, copies over some template files, and even applies customizations to the home page.

In summary, publishing an existing site as a template using PowerShell is the best way to clone a site multiple times. It's a little technical, but with the right script and a little bit of tweaking, you can make this process a lot more manageable.

Before proceeding, make sure to install the SharePoint Online Management Shell. The script I've provided includes a check and installation for the module, but I recommend installing it beforehand.

Open PowerShell as administrator and try my sample code below. Adapting the sample script with some parameters and handling the module installation, we can use the following:

# install the module if you don't already have it

if(

-not (

Get-Module Microsoft.Online.SharePoint.PowerShell -ListAvailable)){

Install-Module Microsoft.Online.SharePoint.PowerShell -Scope CurrentUser -Force

}

# Choices for operations, set to either $true or $false

$exportFromWeb = $true

$exportBackupFile = $true

$createGlobalTemplate = $true

# SharePoint base URL

$baseURL = "ryleybauer"

$companyDisplayName = "Bauer Automate"

# Edit these parameters to define your template

$newSiteTitle = "Quick Project Template"

$shortName = "Projects"

# These variables are generated from the parameters above

$adminURL = ' https://' + $baseURL + '-admin.sharepoint.com'

$siteURL = 'https://' + $baseURL + '.sharepoint.com/sites/' + $shortName

$outFolder = $env:USERPROFILE + '\Downloads\' + $newSiteTitle + ' \ '

$outFile = $outFolder + $newSiteTitle + '.txt '

# Select Source Data

$lists = "Shared%20Documents", "SitePages", "Lists/Losses", "Lists/Projects%20List"

# Connect to SharePoint Online

Connect-SPOService -Url $adminURL

# Generate Script from existing site

if ($exportFromWeb){

$sourceSiteScript = Get-SPOSiteScriptFromWeb -WebUrl $siteURL -IncludeLinksToExportedItems -IncludedLists ($lists)

}

# Optionally create a backup file in the user' s documents folder

if ($exportBackupFile) {

New-Item -Path $outFolder -ItemType Directory

$sourceSiteScript | Out-File -filepath $outFile

}

# Optionally publish as global template and site design

if ($createGlobalTemplate) {

$SiteScript = Add-SPOSiteScript -Title $newSiteTitle -Content $sourceSiteScript

$SiteDesign = Add-SPOSiteDesign -Title $newSiteTitle -WebTemplate 64 -SiteScripts $SiteScript.Id

}

# Get site template list to show the ID of the newly created template and confirm it was successful

Get-SPOSiteDesign

When I first started working with SharePoint Site Designs and Site Scripts, I hadn't used them before and wasn't familiar with their structure. However, I found a great resource in DevFacto's blog post on Getting Started with SharePoint Site Designs and Site Scripts. It helped me understand the anatomy of a site script, which was especially helpful when I needed to split my template file...

...

I didn't want to split the template file

...

I initially didn't want to split the template file, but I learned that site scripts are limited to 100,000 characters. My site had multiple lists and libraries with lots of columns and formatting, so I realized that I had more work ahead of me. Excited for the challenge, I decided to split my file by list and library. This way, it would be more modular for future use and each list/library file could be used individually in a new template if needed. If your template is simple and the file is less than 100,000 characters, then you can skip the next section where I discuss splitting the file.

Reading DevFacto's post was particularly helpful as it gave me a better understanding of the structure of the site script. The post does a great job of outlining the basic structure of the script that I had to use for each file:

The structure of the script helped me to split my file by list and library which made it more modular for future use. My template site had 3 libraries and 7 lists, so I created 10 files. Each file had the same structure and looked something like this:

My template site had 3 libraries and 7 lists, so I had created 10 files. If you opened the files, each of them looked basically like this:

{

"$schema": "schema.json",

"actions": [{

"verb": "createSPList",

"listName": "Shared Documents",

"templateType": 101,

"subactions": [{

"verb": "setDescription",

"description": "Project team can use this Documents Library to store deliverable documents."

}

//EXTRA STEPS HERE

]

}

"bindata": {},

"version": 1

};

Once we put all of that together, and understand the anatomy of a site script, we can clone very complex site templates.

If you take the original script from above and add a few more parameters to check if the script should import one or more files instead, you get the following:

# install the module if you don 't already have it

if (

-not (

Get-Module Microsoft.Online.SharePoint.PowerShell -ListAvailable

)

) {

Install-Module Microsoft.Online.SharePoint.PowerShell -Scope CurrentUser -Force

}

# Choices for operations, set to either $true or $false

$exportFromWeb = $true

$importFromFile = $false

$importFromMultipleFiles = $false

$exportBackupFile = $false

$createGlobalTemplate = $false

# SharePoint base URL

$baseURL = "ryleybauer"

$companyDisplayName = "Bauer Automate"

# Edit these parameters to define your template

$newSiteTitle = "Project Template"

# Select your existing site. The short name is the URL section after "https://bauerautomate.sharepoint.com/sites/SHORTNAME"

$existingSiteShortName = "Projects"

# These variables are generated from the parameters above

$adminURL = ' https://' + $baseURL + '-admin.sharepoint.com'

$siteURL = 'https://' + $baseURL + '.sharepoint.com/sites/' + $existingSiteShortName

$outFolder = $env:USERPROFILE + '\Downloads\' + $newSiteTitle + ' \ '

$outFile = $outFolder + $newSiteTitle + '.txt '

# Select Source Data

$lists = "Shared%20Documents","SitePages","Lists/Losses","Lists/Projects%20List"

# Generate a name for each script - same as above - add as many as needed to match above

$inFile1Name = $newSiteTitle + " - Projects"

$inFile2Name = $newSiteTitle + " - Documents"

$inFile3Name = $newSiteTitle + " - SitePages"

# Input files from existing template that was split into multiple files - add as many as needed, and I recommend 1 per list/library to keep it modular

$inFile1 = $outFolder + ' \' + $inFile1Name + '.txt '

$inFile2 = $outFolder + ' \' + $inFile2Name + '.txt '

$inFile3 = $outFolder + ' \' + $inFile3Name + '.txt '

# Connect to SharePoint Online

Connect-SPOService -Url $adminURL

# Generate Script from existing site

if ($exportFromWeb) {

$sourceSiteScript = Get-SPOSiteScriptFromWeb -WebUrl $siteURL -IncludeLinksToExportedItems -IncludedLists ($lists)

}

# Apply Script from existing single file

if ($importFromFile) {

[string]$sourceSiteScript = Get-Content $inFile1

}

# Optionally create a backup file in the user' s documents folder

if ($exportBackupFile) {

New-Item -Path $outFolder -ItemType Directory

$sourceSiteScript | Out- File - filepath $outFile

}

# Optionally publish as global template and site design from single file

if ($createGlobalTemplate -and -not $importFromMultipleFiles) {

$SiteScript = Add -SPOSiteScript -Title $newSiteTitle -Content $sourceSiteScript

$SiteDesign = Add -SPOSiteDesign -Title $newSiteTitle -WebTemplate 64 -SiteScripts $SiteScript.Id

}

# Apply Script from existing multiple files - add as many as needed

if ($importFromMultipleFiles) {

[string]$sourceSiteScript1 = Get -Content $inFile1

[string]$sourceSiteScript2 = Get -Content $inFile2

[string]$sourceSiteScript3 = Get -Content $inFile3

}

# Optionally publish as global template and site design from multiple files - add as many as needed

if ($createGlobalTemplate -and $importFromMultipleFiles) {

$SiteScript1 = Add -SPOSiteScript -Title $inFile1Name -Content $sourceSiteScript1

$SiteScript2 = Add -SPOSiteScript -Title $inFile2Name -Content $sourceSiteScript2

$SiteScript3 = Add -SPOSiteScript -Title $inFile3Name -Content $sourceSiteScript3

# add as many as needed to the end of this line to add all of the scripts to the site design

$SiteDesign = Add -SPOSiteDesign -Title $newSiteTitle -WebTemplate 64 -SiteScripts ($SiteScript1.Id,$SiteScript2.Id,$SiteScript3.Id)

}

# Get site template list to show the ID of the newly created template and confirm it was successful

Get-SPOSiteDesign

See how we can help today!

Recent Blogs

How to Customize your Modern Microsoft SharePoint Online Site using Classic Features Webparts and Content Types

Thu, 05 Jan 2023 14:08:58 -0700

BONUS: Read more to find the hidden SharePoint classic button for webparts and apps!

As someone who's been around SharePoint for a while, I have gotten used to a few of the classic features that have recently been changed. The other day, I was trying to add a "Photos" library to my site and couldn't find it in the options with the new UI. Turns out they've done a good job of hiding the "classic experience" button. Read below to see the button's new location!

If you're a seasoned veteran to SharePoint and trying to customize your new Modern Microsoft SharePoint Online (SPO) site, then you've come to the right place.

I'm going to show you how to use classic features of SharePoint and web parts to customize your new site.

Let's get started!

Navigate to "Site Contents:"
Select "New"
Choose Option: "App"
Hidden within the first paragraph click on "Classic Experience"
Select your desired App

Below are screenshot guides to better help you...

Some of my favourite Classic SharePoint content types to use are:

Calendar: This is a great way to keep everyone up to date on what's going on in the office. It's also a good way for meeting minutes and other important information. The calendar can be displayed on the front page or within an individual page as well.
Photo / Picture Library: If you need pictures for your site then this is a great place to start! You can add pictures from your local computer or from any other computer connected to the network by using File Explorer, or you can use Microsoft Photos
Wiki: A wiki is a great way to put together Frequently Asked Questions (FAQs) or create knowledge base articles about your business. If you have any questions about something then just ask them here! The community will help out with answers too!
Announcements: This is a great way to let people know when there's an event happening at your company or if it's time for an update on your blog posts or social media accounts like Facebook Twitter , Instagram etc.. You can also add links back into these pages so that people can easily find them

SharePoint is a powerful tool for online collaboration. It's the ideal place to host your company's information and projects, if you are looking for help on how to better use this tool, feel free to connect with me:

If you found this blog post and guide helpful, buy me a coffee

See how we can help today!

Recent Blogs

How to Copy a Modern SharePoint Page

Wed, 28 Dec 2022 17:39:57 -0700

In a past life, I contributed to an article on instructions for how to copy a modern Microsoft SharePoint page from one site collection to another using Microsoft Power Automate. Typically, you can only copy classic and modern pages within the same site collection, unless you're clever and literally treat them as files.

Read the How To Article

See how we can help today!

Bauer Automate - Blog Posts #SharePoint

5 Business Processes That Are Still Shockingly Manual (and Easy to Automate)

1. Approval Workflow Automation (Time Off, Purchases, Expenses)

2. Repetitive Data Entry and System-to-System Automation

3. Document Automation and File Management

4. Automated Reporting and Workflow Automation

5. Business Process Automation for Onboarding

Ready to Automate the Work That Slows Your Team Down?

From Manual to Automated: Where Microsoft's Power Platform Delivers the Biggest ROI

Why Manual Processes Quietly Kill ROI

The 5 Areas Where Power Platform Delivers the Biggest ROI

1. Request & Approval Workflows

2. Data Collection & Validation

3. Reporting & Decision Visibility

4. Document Management & Metadata Automation

5. System Integration Without Custom Code

Why Power Platform ROI Is So Strong

Final Thought

Ready to Automate the Work That Slows Your Team Down?

Two Years of Reflection at the CPPUG — And Why 2026 Has Us Excited

A Community That Just Keeps Showing Up

A Big Milestone: The Power Platform Conference

Looking Ahead to 2026

A Huge Thank You

Want to Be A Part of the CPPUG Team?

Automating Microsoft Teams Memberships with Power Automate & Graph API: One Nite Band Workflow

How We Streamlined Musician Scheduling Using Power Platform & Microsoft Graph

Introduction: From Simple to Sophisticated

Project Goal: Automate Smart Role-Based Channel Assignment in Microsoft Teams

Key Technical Learnings and Challenges

1. Internal vs. External Users: It's Not Just a Checkbox

2. Why concat() Almost Broke the Flow

3. User GUIDs Are Mandatory for Graph API

4. Schema Errors & Permission Pitfalls

5. Array Variables: Your Flow’s Best Friend

6. Unexpected Microsoft Teams Constraints

Real-World Impact: From Jam Nights to Project Teams

Final Thoughts: Beyond the Flow

Want to Learn More or Set Up A System that Works for You?

Using Power Automate to Create a Photo Library and Add it to the Navigation

Adding a photo library programmatically

Using PowerShell to Save or Clone an Existing SharePoint Online Site to Publish a the Global Template to the "From Your Organization" Menu

Recent Blogs

{{title}}

How to Customize your Modern Microsoft SharePoint Online Site using Classic Features Webparts and Content Types

Recent Blogs

{{title}}

How to Copy a Modern SharePoint Page

Recent Blogs

{{title}}