Showing results for 
Search instead for 
Did you mean: 
Not applicable

Setting the default column value of a subfolder in a document library using Power Automate

I have a Flow that automatically creates project folders in a document library on SharePoint based on a form response and I need different folders to have different default column values to make use of searching using metadata. The Folder structure is Client/Location/Project so I want the folders in the client folder to have a default value of the client, the location to have default values of client & location and I want the project folder to have default of the previous as well as the project number.


The issue i'm having is that I can set the default column value for the library but I run into issues when I try to set the default values of the subfolders. The error i'm receiving is "List 'xxxxxxxxxx/xx xxxxxx' does not exist at site with URL 'https://xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'.
clientRequestId: c2e9facc-fe0d-4caf-a611-25f2c6fe21b8
serviceRequestId: 28bfa59f-5061-b000-a4fc-4d19b87acc90"


See screenshot below of configuration:




Any help would be appreciated!



Most Valuable Professional
Most Valuable Professional

Hi @Anonymous,


For me it's not entirely clear if you want to update the default value of a column or if you just want to update the metadata of a list item, in this case a folder.


So, I have created REST API examples for both scenarios. Hope this helps a bit?


1. Update the default value of a document library field. In this case I am setting the default value of the field to Contoso Sports.








  "Accept": "application/json;odata=verbose",
  "Content-Type": "application/json;odata=verbose",
  "X-HTTP-Method": "MERGE",
  "IF-MATCH": "*"




  "__metadata": {
    "type": "SP.Field"
  "DefaultValue": "Contoso Sports"




2. Update the value of that same field for an item in the document library. In this example I am first retrieving the ListItemEntityTypeFullName. I am using that value for the type in the second request. In this case I am setting the value of the field of the folder item to Contoso.








  "Accept": "application/json;odata=nometadata"










  "content-type": "application/json; odata=verbose",
  "accept": "application/json; odata=verbose",
  "IF-MATCH": "*",




	"__metadata": {
    "type": "@{outputs('Send_an_HTTP_request_to_SharePoint_-_ListItemEntity')?['body/ListItemEntityTypeFullName']}"
  "@{variables('FieldName')}": "Contoso"




Happy to help out! 🙂

Interested in more #PowerAutomate #SharePointOnline or #MicrosoftCopilotStudio content?
Visit my blog, Subscribe to my YouTube channel or Follow me on Twitter

Not applicable

Thank you for your detailed reply, for the 2nd one I get an error saying "Invalid JSON. A comma character ',' was expected in scope 'Object'. Every two elements in an array and properties of an object must be separated by commas."




However, the main issue I have and need resolving is setting a default value in a column specifically for the project name subfolder e.g. Contoso/ProjectName



Not applicable

I think I have the same need as the original poster - who did not seem to have gotten his issue resolved.


We are trying to use Power Automate to set the default column value at the folder level. Ie. corresponding to the following UI in Sharepoint - Not the general default value for the column in the document library.



Any ideas on how to achieve this?

Hi @Anonymous did you ever get this working.  I am trying to do the same thing

Not applicable

I'm assuming this was never resolved? 


Is there a restapi that allows us to set this setting?

Super User
Super User

There are a few open threads around this request and I figured it out today so thought I'd drop what I figured...


And, a warning:


Don't try this on a Prod library! Test it out and get it working first. (Luckily I wasn't as stupid as I normally am and only tried in test sites.)

First, my goal was to set default values on sub-folders. 

Here is my Flow:



One caveat - this won't work until you've modified one default, as this seems to create the file in the background. (For myself, I have one piece of Library metadata that will default across the board, so I am going to see if I can just set that through API on its own - but wanted to post this first. UPDATE: Updating one default didn't work to trigger the HTML creation. Oh well.) 

Step 1)
Initialize a string variable.

Step 2)
Get the client_LocationBasedDefaults.html content.


Step 3) I have a Compose for step 3, but that's just because it kept failing based on everything I was reading, so I wanted to look at what the DEFAULT output was from this file. If you want to see, you will do this in a Compose:  



Step 4) Build your defaults! It's not even difficult it's just SO PICKY. Here I am setting values for 2 different folders.





 <MetadataDefaults><a href="/sites/Intranet/TestDefaults/Test1"><DefaultValue FieldName="TextTest">bad</DefaultValue></a><a href="/sites/Intranet/TestDefaults/Test2"><DefaultValue FieldName="TextTest">good</DefaultValue></a></MetadataDefaults> 




Step 5) Cram it back into the file and rejoice.


Here's what it looks like, with some more complex sends... showing that it inherits properly.


I've never been so happy to see those horrible little green gears. Flowers? They kind of look like ICQ flowers.

PS: This works with MMD as well but you need to structure it as -1;#LABEL|LABELGUID



Did this answer your question? Please mark it as the solution.
Did it contribute positively towards finding the final solution? Please give it a thumbs up.

I answer questions on the forum for 2-3 hours every Thursday!

New Member

Thank you so much for this! I did get it to work by testing what you provided above. However, when I'm trying to do multiples of the same folder on different site columns, it completes, but only changes the first one. Any idea of my error?

<a href="/sites/Projects/TestDefaults/Test1"><DefaultValue FieldName="State">TX</DefaultValue></a>
<a href="/sites/Projects/TestDefaults/Test1"><DefaultValue FieldName="Vesper Dept">Projects</DefaultValue></a>
<a href="/sites/Projects/TestDefaults/Test2"><DefaultValue FieldName="State">CA</DefaultValue></a>
<a href="/sites/Projects/TestDefaults/Test2"><DefaultValue FieldName="Vesper Dept">Projects</DefaultValue></a>

Thank you for you blogpost.

In my flow, a new folder is created and then I want to set the default values for the columns.
I can run the flow successfully and the default values are set on the newly created folder, however, the the default values of the previously created folders are deleted.
In my case the file "client_LocationBasedDefaults.html" is overwritten, so that only the folder created in the flow has a default value.

How do I make sure the new value is added in to the current client_LocationBasedDefaults.html file instead of creating a new client_LocationBasedDefaults.html every time.

You can just create a condition to query for that file - if it finds it, then, just copy the text out and append your updates. If it doesn't, then, create a new one.


Did this answer your question? Please mark it as the solution.
Did it contribute positively towards finding the final solution? Please give it a thumbs up.

I answer questions on the forum for 2-3 hours every Thursday!

Thanks for this post but i have given it many tries doing exactly as you do but i am unable to get this working in anyway. I am able to get this working in powershell PNP (i am at the point to just build a function app for this).

It is a crucial function to have so is there perhaps more information you can give or test if this still works as expected

When you have multiple for the same folder, the syntax is different. Try something like this:

<a href="/sites/Projects/TestDefaults/Test1"><DefaultValue FieldName="State">TX</DefaultValue><DefaultValue FieldName="Vesper Dept">Projects</DefaultValue></a>
<a href="/sites/Projects/TestDefaults/Test2"><DefaultValue FieldName="State">CA</DefaultValue><DefaultValue FieldName="Vesper Dept">Projects</DefaultValue></a>
Helper I
Helper I

Okay y'all, buckle up. I know this is more than two years old but it's basically the only post I found while trying to do this so hopefully this saves someone else the headache.


All kudos to @Rhiassuring whose work above was the foundation for this post. I literally would not have known where to start without them.


Here's how I figured out how to add new defaults to the existing defaults. Important note here that these steps assume the client_LocationBasedDefaults.html file already exists, which it will not unless at least one column default has been set through the UI. In my use-case I do not have a need to programmatically create new client_LocationBasedDefaults.html files, only update the existing one for an existing library, so I did not spend time trying to figure that out.


Step 1. Get the path to your client_LocationBasedDefaults.html file

Go to your SharePoint site’s document library (at the top level) through a web browser and then copy the URL, it will look something like this:


Now replace the “AllItems.aspx” at the end of your URL with “client_LocationBasedDefaults.html” like


Step 2. Add the “Send an HTTP request to SharePoint” action in your Flow. Pick your site and GET as the method. For a URL like my above example, the Uri would be as follows:

_api/Web/GetFileByServerRelativePath(decodedurl='/sites/RR-Catalog/Shared%20Documents/Forms/client_LocationBasedDefaults.html ')/$value?binaryStringResponseBody=true

Don’t populate Headers or Body sections.


Step 3. Modify the existing client_LocationBasedDefaults.html content to be able to use later.

The output of Step 2 is going to be the current folder defaults for that library. It will look something like this: (line breaks added for readability – don’t put line breaks in your actual Flow!)


<a href=\"/sites/RR-Catalog/Shared%20Documents/Anvils\"><DefaultValue FieldName=\"Class\">Anvil</DefaultValue></a>

<a href=\"/sites/RR-Catalog/Shared%20Documents/Disguises\"><DefaultValue FieldName=\"Class\">Costume</DefaultValue></a>

<a href=\"/sites/RR-Catalog/Shared%20Documents/Cooking%20Utensils\"><DefaultValue FieldName=\"Class\">Appliance</DefaultValue></a>

<a href=\"/sites/RR-Catalog/Shared%20Documents/Jets%20%26%20Motors\"><DefaultValue FieldName=\"Class\">Transport</DefaultValue></a>


We need to insert our new defaults into this file before the </MetadataDefaults> closing tag, and we need to remove all the backslashes (\) - the string you put together to put in the HTTP request later should have NO backslashes in it. Don't replace them - remove them. Use a compose and nest a decodeBase64 formula within the replace formula:

replace(decodeBase64(body(‘Step_2_Action’)?['$content']), '\', '')

Then we need to remove the closing Metadata tag so that we can append our changes in a later step:



Step 4. Determine your new defaults.

All of the folders in the above example are located at the top level of the library. As you go deeper into the folder structure the syntax of the metadata defaults simply extends the URL. For example, “Shared Documents > Jets & Motors > Jet Bike Kit” would be:

<a href=\"/sites/RR-Catalog/Shared%20Documents/Jets%20%26%20Motors/Jet%20Bike%20Kit\"><DefaultValue FieldName=\"Class\">Transport</DefaultValue></a>

Notice how Jet Bike Kit became Jet%20Bike%20Kit and Jets & Motors became Jets%20%26%20Motors? If you are building your own path out of dynamic values in Flow, you have to account for the required formatting. Replace all spaces with %20:

replace({dynamicvalue}, ‘ ’, ‘%20’)

Look out for other types of special characters in your folder names. Don't have any if you can help it, but if you do you will have to replace them with what SharePoint actually sees - look at the URL you get when you navigate to that folder in the library to get an idea of what SharePoint sees as the actual folder path and name. Once you know that, you can add steps in the flow to replace or remove certain special character from the dynamic values before you plug them into your final string. In this case, we know that & = %26, so we would write a replace formula for the & symbol:

replace({dynamicvalue}, ‘&‘, ‘%26’)

This only applies to the path, the default value itself does not need to be transformed.

In my scenario, I am updating a folder’s metadata based on values in a list item. The list items are categorized by the top-level folders, meaning I have a field on the list that tells me if the item is Anvils, Disguises, Cooking Utensils, or Jets & Motors. So, I would do something like this:


replace(replace(triggerOutputs()?['body/Class'], ‘ ’, ‘%20’), ‘&’, ‘%26’)
replace(triggerOutputs()?['body/Title'], ‘ ’, ‘%20’)
<a href="/sites/RR-Catalog/Shared%20Documents/@{outputs('Compose_Path_Class')}/@{outputs('Compose_Path_Title')}"><DefaultValue FieldName="SKU">@{triggerOutputs()?['body/SysID']}</DefaultValue></a>


Step 4a. What if I want to add more than one default value to a folder?

If you need to set multiple defaults for the same folder, you need to do that within the <a> tag, so you wouldn’t close the tag until you’ve covered them all. Add more by adding additional <DefaultValue> tags after the URL. For example:

<a href=\"/sites/RR-Catalog/Shared%20Documents/ Jets%20%26%20Motors/Tennis%20Balls\"><DefaultValue FieldName=\"Class\">Transport</DefaultValue><DefaultValue FieldName=\"Department\">Sports</DefaultValue></a>

In this case you would likely want to build each <DefaultValue FieldName=\"{column}\">{defaultvalue}</DefaultValue> statement separately and then combine them all into one statement with the folder path. I prefer compose actions over variables, but it may make more sense to have a string variable and an append to string variable action if you have a lot of default values you want to add to a single folder.


Step 4b. What if I want to update more than one folder at a time?

If you will be adding multiple folders in one flow, that basically equates to adding multiple lines. I would recommend using an apply to each if possible (and/or call a subflow) to go through the steps to modify and combine your default values for each folder you would want to update. In this scenario, you would have to add an additional action after my Compose New Path that is an append to string variable so that your output will capture all the options. Then wherever I am plugging in outputs('Compose_New_Path') you would plug in the string variable.


Step 5. Combine the existing with the new.

This is thankfully a simple concat:

concat(outputs('Compose_LocationBasedDefaults'), outputs('Compose_New_Path'), ‘</MetadataDefaults>’)


Step 6. Upload it back to SharePoint

Use the “Send an HTTP request to SharePoint” action again, with PUT as the Method and a Uri like:

_api/Web/GetFileByServerRelativePath(decodedurl='/sites/RR-Catalog/Shared%20Documents/Forms/client_LocationBasedDefaults.html ')/$value


In the body, enter the output from your concat in Step 5.


In my flow I ended up combining a bunch of these steps, but I would strongly recommend you create each one separately first and make sure it works on a test library before doing that yourself. I would also recommend saving the original output from the first HTTP request and adding that into a compose while you’re building it, because as you test you will be appending on to your previous tests, which can compound mistakes and make it hard to tell when you’ve succeeded. If you have the OG code ready in a compose, you can swap that output back into your flow in between real tests to ‘reset’ the file.

Hi all! You mentioned that it works for Managed Metadata Column, but we need specific template 1;#LABEL|LABELGUID. But I don't understand where we can find the first number. With random number it doesn't work. Do you know the secret, how we need to set those values?) 

Go to the Term Store (where you created the Managed Metadata in the first place - can be found by adding /_layouts/15/SiteAdmin.aspx#/termStoreAdminCenter to the end of your site address) click on the term you want the ID for, then click on the "Usage settings" tab and copy the Unique identifier:



Then you want it formatted like this:



This is what you will need whenever referencing the Managed Metadata basically anywhere that's not a user interface - like if you want to Switch on it in a Power Automation flow, the Case would be in that same format.

Frequent Visitor

Both posts here from @Rhiassuring and @RathwynAE were great here and I was almost there. 

I have created a Team create form in a powerapp that querys the Term Store for the Customer so that the users can have their documents automatically tagged from the start. 

I got as far as being able to set the managed metadata default value on to a column, but when testing, the documents are not being 'tagged' and the values when clicking on the column in the default column values settings, the defaul setting is not actually set.

I tried creating the client_LocationBasedDefaults.html file, but had no luck. It really feels like that is the key. Manually setting it isnt a solution as the customer wants this flow to skip needing to touch the site before handing it over to the owners. 

Anyone got any ideas about creating that file? 

Hi Karina, 

From my work this week, i have found that that number is always '-1', so you can build the structure in a compose action. It may have not been working as you were using '1'?

Regular Visitor

The first number isn't the standard -1 WssId, it's the ID for the metadata term in your site's locally cached TaxonomyHiddenList:



Browse to that list and show the columns 'IdForTerm' and 'ID' -- the ID is what you need to compose your string 'ID;#LABEL|LABELGUID'. The IDs are auto-increment and apply to any metadata used in the Site Collection, doesn't matter what term set they belong to or what List they are used in. When you manually set a metadata value (via a form, using the library column defaults page, etc.) and use a term for the first time it will add it to the TaxonomyHiddenList and you'll get a new ID generated.


Even thought you know what the next ID number will be, updating client_LocationBasedDefaults.html with new, sequential IDs won't work since it doesn't actually add them to the TaxonomyHiddenList. You need to get the terms added to TaxonomyHiddenList first so you can retrieve their IDs to then write to client_LocationBasedDefaults.html. You could create a test List, use Flow to loop through every term in your set and assign it to a List item. That would populate TaxonomyHiddenList with all your terms and IDs so you could then query that list to get the IDs you would need. This is what I've had to do since I don't have permission to run Powershell.

Hi RathwynAE,

Can you please share the Screen shot of the full flow because I am trying to do the same but I am getting errors.

Hey there,


I also had a customer with the request to create the client_LocationBasedDefaults.html file, without manual input before. So I fiddled around a bit and found a PowerShell script to create a client_LocationBasedDefaults.html file:


I tried converting this into a flow and got this working:

Save Default Values.PNG

Hope this helps! 😊

Helpful resources


Summer of Solutions | Week 3 Results | Win free tickets to the Power Platform Conference

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24  17 @Anil_g  7 @ManishSolanki  13 @eetuRobo  5 @David_MA  10 @VishnuReddy1997  5 @SpongYe  9JhonatanOB19932 (tie) @Nived_Nambiar  8 @maltie  2 (tie)   @PA-Noob  2 (tie)   @LukeMcG  2 (tie)   @tgut03  2 (tie)       Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate  @Deenuji  12@ManishSolanki 19 @Anil_g  10 @NathanAlvares24  17 @VishnuReddy1997  6 @Expiscornovus  10 @Tjan  5 @Nived_Nambiar  10 @eetuRobo  3 @SudeepGhatakNZ 8     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22  

Copilot Cookbook Challenge | WINNERS ANNOUNCED | Win Tickets to the Power Platform Conference

We are excited to announce the "The Copilot Cookbook Community Challenge random winners have been selected for the Challenge.  Thank you to everyone who participated in this challenge.    Copilot Cookbook Gallery:Power Apps Cookbook Gallery: 1. @swaminawale  1. @renatoromao     2.  @SpongYe  2.   @nickpotts10  *Please note if for any reason a winner declines, we will have another random drawing.   Check out all of the Cookbook Submissions: 1. Copilot Studio Cookbook Gallery: 2. Power Apps Copilot Cookbook Gallery:   There will be 5 chances to qualify for the final drawing: Early Bird Entries: March 1 - June 2Week 1: June 3 - June 9Week 2: June 10 - June 16Week 3: June 17 - June 23Week 4: June 24 - June 30WINNERS ANNOUNCED - JULY 8th     At the end of each week, we will draw 5 random names from every user who has posted a qualifying Copilot Studio template, sample or demo in the Copilot Studio Cookbook or a qualifying Power Apps Copilot sample or demo in the Power Apps Copilot Cookbook. Users who are not drawn in a given week will be added to the pool for the next week. Users can qualify more than once, but no more than once per week. Four winners will be drawn at random from the total qualifying entrants. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once. If they are drawn multiple times, another user will be drawn at random. Prizes:  One Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value, does not include travel, lodging, or any other expenses) Winners are also eligible to do a 10-minute presentation of their demo or solution in a community solutions showcase at the event. To qualify for the drawing, templates, samples or demos must be related to Copilot Studio or a Copilot feature of Power Apps, Power Automate, or Power Pages, and must demonstrate or solve a complete unique and useful business or technical problem. Power Automate and Power Pagers posts should be added to the Power Apps Cookbook. Final determination of qualifying entries is at the sole discretion of Microsoft. Weekly updates and the Final random winners will be posted in the News & Announcements section in the communities on July 29th, 2024. Did you submit entries early?  Early Bird Entries March 1 - June 2:  If you posted something in the "early bird" time frame complete this form: if you would like to be entered in the challenge. Early Bird Submissions: @renato Week 1 Results:  Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1.  @Mathieu_Paris 1.   @SpongYe 2.  n/a2.   @Deenuji 3.  n/a3.   @Nived_Nambiar  4.  n/a4.   @ManishSolanki 5.  n/a5.    n/a   Week 2 Results:  Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1. Kasun_Pathirana1. ManishSolanki2. cloudatica2. madlad3. n/a3. SpongYe4. n/a4. n/a5. n/a5. n/a     Week 3 Results:  Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1. Parul_Yadav_Neo1. n/a2. SpongYe2. n/a3. n/a3. n/a4. n/a4. n/a5. n/a5. n/a   Week 4 Results:  Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1. @nickpotts10  1. @ShrushtiShah  2. @Suniti_0020 2. @swaminawale 3. n/a3. @farukhis786 4. n/a4. @ManishSolanki  5. n/a5.  n/a

Important Update for Community Platform Access | READ ONLY July 16-22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Tuesday Tip | How to Become a Community Blog Author

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   This Week's Topic: How to Become a Community Blog Author We want YOU to be part of the community blog! Sharing your knowledge of Power Platform is an essential part of our community! Here's why:   It helps create a vibrant and dynamic community of makers who can learn from each other’s experiences and insights.It provides a platform for collaboration and innovation, where members can share their ideas and work together to develop new solutions.It helps promote Power Platform by showcasing its capabilities and real-world applications.It helps build trust and credibility in the community because you are providing valuable information and resources your fellow community members can use to improve their skills and knowledge. By sharing your knowledge of Power Platform in the community blog, you help us create a more engaged and informed community, better equipped to tackle complex challenges. To get started with blogging across the Power Platform communities, please visit the following links:   Power Apps: Power Automate: Copilot Studios: Pages:   When you follow the link, look for a button like the one below on the right rail of your community blog, and let us know you're interested. We can't wait to connect with you and help you get started. Thanks for being part of our incredible community--and thanks for becoming part of the community blog!  

June 2024 Community Newsletter

It's time for the June Community Newsletter, where we highlight the latest news, product releases, upcoming events, and the amazing work of our outstanding Community members.   If you're new to the Community, please make sure to follow the latest News & Announcements and check out the Community on LinkedIn as well! It's the best way to stay up-to-date with all the news from across Microsoft Power Platform and beyond.    COMMUNITY HIGHLIGHTS   Check out the most active community members of the last month! These hardworking members are posting regularly, answering questions, kudos, and providing top solutions in their communities. We are so thankful for each of you--keep up the great work! If you hope to see your name here next month, follow these awesome community members to see what they do!   Power AppsPower AutomateCopilot StudioPower PagesWarrenBelzcreativeopinionExpiscornovus Fubar AmikNived_NambiarPstork1OliverRodriguesmmbr1606ManishSolankifernandosilvaragavanrajanBCBuizerExpiscornovusrenatoromaoLucas001timlAlexEncodianViswavEmadBeshaiDBO_DVDeenujiUmiantaChrist0fGochixVishnuReddy1997citron-trucmandelaVishalJhaverieetuRoboJohanTprathyooanandm08VictorIvanidzenicoxrfm1964shashankbhidepaulbeck1 rpaa   LATEST NEWS Summer of Solutions 2024 The Summer of Solutions challenge kicked off this month - an amazing Microsoft Community initiative to win free tickets to the Power Platform Community Conferencethis September in Las Vegas. The challenge is NOW OPEN to all #PowerPlatform community members and will consist of four weekly entry periods until July 14th, 2024. Click the image below to find out more on how you can win free tickets to #PPCC24 by entering the Summer of Solutions TODAY!   Microsoft Customer Stories We're constantly working with an array of great businesses across the globe to assist them in taking advantage of the latest business applications technology. If you'd like to find out more about their low code journeys, click the image below to view our playlist of Customer Stories to discover how Accenture, Lumen Technologies, Cineplex, and many more, are streamlining their business processes with Microsoft Power Platform.     Microsoft Leap Program Have you heard of Microsoft Leap - a global program designed to recruit, develop, and upskill unconventional talent for careers in the tech space. Microsoft Leap organizes a number of pathways into the industry, including the recent "NFL Legend Cohort - Technical Program Management" run jointly with the NFL Player Care Foundation (PCF) who are dedicated to helping retired players improve their quality of life. Click the image below to find out more about the great day shared at the Redmond campus and be sure to visit the Microsoft Leap website to discover how this amazing initiative is helping re-launch the lives of countless individuals.       UPCOMING EVENTS Biz Apps Partner Summit | Seattle | July 24-25 It's not long now until the Biz Apps Partner Summit, which takes place at the Hilton Bellevue in Seattle on July 24-25, 2024. This event is the perfect place to network, connect, and learn how to scale your Microsoft practice, drive profitable revenue, and dazzle your customers! There's a great selection of speakers, including the likes of Tom Patterson, Donald Kossmann Joseph Corigliano, Cecilia Flombaum, Peter Jensen, John Siefert, Becky Lymberis, Daniel Rippey, and many more. Click the image below to find out more and register today!     TechCon365 & Power Platform Conference | D.C. | August 12-16 Things are hotting up for the next TechCon365 & PWRCON Conference in Washington D.C. on August 12-16, 2024. Featuring the likes of Tamara Bredemus, Sunny Eltepu, Lindsay Shelton, Brian Alderman, Daniel Glenn, Julie Turner, Jim Novak, John White, Jason Himmelstein, Luc Labelle, Emily Mancini, MVP, UXMC, Fabian Williams, Emma Wiehe,and many more, this is the perfect event for those that are looking to gain invaluable insights from industry experts. Click the image below to grab your tickets today!     Power Platform Community Conference | Vegas | Sept. 18-20th Are you ready to come and join the fun in Las Vegas this September at PPCC24? This event is the perfect place to connect with fellow business applications enthusiasts and share your knowledge with the worldwide Microsoft Community. Now's your chance to hold all the aces. Just click the image below to find out more and we hope to see you go ALL-IN this September in Las Vegas!     For more events, click the image below to visit the Community Days website.  

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (1,984)