No Code SharePoint Site Creation with a Flow

sharepoint automated site creation

No developer skills required! Here’s how to automate SharePoint site creation using Power Automate with a few no-code approaches.

If you’ve ever needed to create multiple SharePoint sites with consistent settings and configurations, you know how time-consuming and repetitive the process can be. The good news is that there are several ways you can automate this entire process using Power Automate – without writing a single line of code!

In this post, I’ll show you three methods for automated SharePoint site creation, along with the triggers and post-creation actions that make this process truly powerful. Let’s dive in!

Three Ways to Create Sites Automatically

There are three primary approaches to creating SharePoint sites using Power Automate:

Infographic comparing SharePoint site creation methods using Power Automate. It includes three approaches: SharePoint HTTP, Office 365 group, and Microsoft Teams. Each method is associated with pros and cons, along with visual icons representing actions and components.

1. Send an HTTP Request to SharePoint

This method utilizes the “Send an HTTP request to SharePoint” action in Power Automate to create a basic SharePoint site based on traditional templates. The key advantages:

  • Creates a standalone SharePoint site (without a Microsoft 365 group)
  • Offers detailed control over site configuration
  • Uses SharePoint’s web services with a simple code snippet

The HTTP request includes specific parameters for site creation:

{ "request": 
  { "Title": "**TITLE**", 
    "Url": "https://YOURTENANT.sharepoint.com/sites/**TITLE**", 
    "Lcid": 1033, 
    "ShareByEmailEnabled": false, 
    "Description": "**DESCRIPTION**", 
    "WebTemplate": "STS#3", 
    "Owner": "**OWNER**" 
   } 
}  
Screenshot of a Power Automate flow for sending an HTTP request to create a SharePoint site, showing parameters, initialization of variables, and detailed request body configuration.

2. Create a Microsoft 365 Group

This method uses the Create an Office 365 group action, which automatically includes a SharePoint site as part of the group creation process. Key points:

  • Creates a complete Microsoft 365 group ecosystem including:
    • SharePoint site
    • Email address
    • Team calendar
    • Planner plan
  • Requires Microsoft 365 admin or SharePoint admin permissions
  • Creates public groups by default (extra step needed for switching to private)
  • Offers less customization compared to the HTTP method
Screenshot of a Microsoft Power Automate interface displaying parameters for creating an Office 365 group, including fields for Display Name, Description, Mail Nickname, Security Enabled, and Mail Enabled.

3. Create a Microsoft Team

The third option uses the “Create a team” action in Power Automate, which creates:

  • A Microsoft Teams team
  • A SharePoint site
  • A Microsoft 365 group

This approach is ideal when you need full collaboration capabilities and allows you to choose whether the group is public or private during creation.

User interface for creating a team in Power Automate, showing fields for team name and description, along with steps for triggering a flow and adding members.

Which Method Should You Choose?

The method you select depends on your specific requirements:

FeatureHTTP RequestOffice 365 GroupCreate a Team
Site TypeSharePoint site onlyMicrosoft 365 GroupMicrosoft 365 Group + Teams
Email/CalendarNoYesYes
PlannerNoYesYes
Teams IntegrationNoNo (can add later)Yes
Default PrivacyN/APublicavailable in the action
Permission ManagementManualGroup-basedGroup-based

If users need shared calendars, email, or Teams channels, the Microsoft 365 Group or Teams approaches make sense. For simpler document collaboration, a standalone SharePoint site might be sufficient.

Site Provisioning Best Practices

When setting up your automated flow, consider gathering these essential metadata fields:

  • Site Name: The display name for your site
  • Site Description: A brief overview of the site’s purpose
  • URL: The web address (remember to replace spaces with underscores or hyphens)
  • Site Owner: Who will manage the site
  • Site Template/Design: Any custom designs to apply

Creating Your First Flow: Step by Step

Here’s how to build a basic site creation flow:

  1. Create a manual trigger form to collect site information:
    • Site Name
    • Site Description
    • Site Owner (Person field)
  2. Modify the site name for the URL:
    • Initialize a variable for the site name
    • Use replace(triggerBody()['siteName'], ' ', '_') to replace spaces with underscores
  3. Add your site creation action (either HTTP request, Office 365 Group, or Teams creation)
  4. Add a delay (1-2 minutes) to ensure the site is fully provisioned before any additional customizations
  5. Customize your new site (optional):
    These are some options that you can choose to add on, as some ideas, and I cover each of them in the video below.
    • Copy a template homepage from an existing site
    • Apply a site design
    • Create standard folders or document libraries
    • Add default documents

Post-Creation Customizations

Once your site is created, you can automate various customizations:

Copying a Homepage Template

To copy an existing homepage to your new site:

  1. Add a SharePoint Copy File action
  2. Specify the source site and homepage file
  3. Set the destination to your new site’s “site pages” library
  4. Add an HTTP request action to set it as the default homepage
Screenshot of Power Automate's 'Copy file' action parameters, showcasing fields for current site address, file to copy, destination site address, destination folder, and overwrite settings.
Screenshot showing the parameters and settings for sending an HTTP request to SharePoint to set the default homepage.
{
  "__metadata": {
    "type": "SP.Folder"
  },
  "WelcomePage": "SitePages/YOURPAGENAME.aspx"
}

Adding Default Documents

To populate your site with template documents:

  1. Use the Get Files action to retrieve files from a template site
  2. For each file/folder:
    • If it’s a folder, create a new folder in the destination
    • If it’s a file, copy it to the new site

Applying Site Designs

If your organization has custom site designs created via PowerShell, you can apply them through Power Automate:

Screenshot of Power Automate interface showing parameters for sending an HTTP request to SharePoint, including site address, method, URI, and body.
{
  'siteDesignId': 'f0a3abf4-afe8-4409-b7f3-484113dee93e',
  'webUrl': 'https://wonderlaura.sharepoint.com/sites/YOURSITENAME'
}

Triggering Your Site Creation Flow

While we’ve focused on manual triggers, you can also initiate your flow through. There’s more of a capability of adding maybe an approval process if you need site requests to be approved my someone before the site gets created.

  • SharePoint list items: Trigger when a new request is added to a list
  • Microsoft Forms: Use a form to collect site information
  • Power Apps: Create a custom app for site requests

Key Takeaways

  • Automated site creation saves time and ensures consistency
  • Power Automate offers multiple methods without requiring coding skills
  • Consider which components users need (SharePoint only vs. full Microsoft 365 Group)
  • Post-creation actions like applying templates and copying files add significant value
  • Properly managing URLs (removing spaces) improves searchability

Ready to start automating your SharePoint site creation? Check out our training courses at iwmentor.com for more Microsoft 365 productivity tips!

Would you like to learn Power Automate? Check out my very own online 10 hour comprehensive course!

Here is the associated video for this post:

Leave a Reply