If you’ve ever tried to create a new item on a SharePoint list, you may have noticed that the form always includes an Attachments field that can’t be hidden like other columns. If your process doesn’t require attachments or you’d like to prevent users from uploading documents to the list, you’re likely wondering how to get past this obstacle.
End of a SharePoint form with the Attachments field | Click to enlarge
Note Be aware that if users previously utilized the Attachments field, this action would delete all attachments they’ve already uploaded on all list items.
In this post, I’ll highlight the 5 simple steps involved in removing the attachments field for a list’s new item form.
How to remove the attachments field from a list’s new item form
Click Settings | List Settings
Location of List settings | Click to enlarge
Select Advanced settings
Location of Advanced settings in List Settings | Click to enlarge
Set the Attachments radio button to Disabled
Advanced list settings showing the Attachments setting as Disabled | Click to enlarge
Click OK
You’ll receive a warning making sure you’re aware that this action deletes all attachments (if there are any). Click OK.
Warning when saving Attachments setting as Disabled | Click to enlarge
And that’s it! Now your forms will only show fields you’ve created and configured.
End of a SharePoint form without the Attachments field | Click to enlarge
If you’re not able to access or modify List settings, you may not have high enough permissions to modify the list. Check with your site owner to see if they can assist.
Attachments are secondary to the list/form data itself and should be used for specific business processes, such as attaching receipts for reimbursement requests or perhaps photos or screenshots for facility or issue trackers. If the document is independently important, it should be stored in a document library.
Also keep in mind that attachments don’t have version history, cannot be renamed or reorganized without downloading/re-uploading, and they are not searchable in Microsoft 365. If you need to search for attachments, you should store them in a document library instead of a list – and you can always use a lookup column or hyperlink column to connect the list and library.
Do you want to send someone a direct link to an approval request in Power Automate? This can be useful if you want to remind them via chat or email or assign them a task in Planner or To Do. In this blog post, I’ll show you how to get a link to a specific approval request’s link that you can use in different Power Automate flow concepts.
You may already know that Power Automate has three approval related actions: Start and wait for an approval, Wait for an approval, and Create an approval. Each of these actions has different dynamic content available for later steps. To get a link to a specific approval request, we need to use the Create an approval action because it gives us access to the Respond link dynamic content. This is the link that will take users directly to the approval board in Power Automate with their approval task open awaiting response.
Respond link dynamic content | Click to enlarge
How can you use this link? For example, imagine you want to create a flow that runs when a new request is created in SharePoint and creates a Planner task for the approver with the link to the approval request.
Illustration of the overall concept here – a link to an approval request | Click to enlarge
Here are the steps for this particular request scenario:
How to create a Power Automate flow that assigns Planner tasks containing links to approval requests
Note: For sensitive information, like leave requests, you’ll want to be mindful of PII and privacy and consider email or chat or other ways to use the link so only individuals who should see sensitive content can. This is merely an example of how you might use Planner tasks for any request scenario.
For your flow’s trigger, search for SharePoint and select When an item is created. Configure the trigger by selecting the site and list where you want to monitor new items. For example, you might choose your HR site and the Leave request list.
Click Add an action and search for Create an approval. Configure the approval details as you need. In our example, you might want to request approval from the employee’s manager and set the title to “Leave request approval.” If you intend to send custom notifications via email, planner tasks, etc., click Show advanced options and set Enable notifications to No. This will prevent approvers from receiving multiple notifications about the same approval request.
The first three steps of our approval flow | Click to enlarge
Click Add an action and search for Create a task (Planner). Select the plan and bucket where you want to create the task. For example, you might choose your specific team’s plan and the Pending tasks bucket.
Planner task configuration | Click to enlarge
Click Add an action and search for Update task details (Planner). Select the task ID from the previous Planner action. In the References section, fill in the following fields: References Alias is the text that will be clickable. References Resource will be the Respond link dynamic content from the Approval step. And References Type will be Other.
Update task details configuration | Click to enlarge
Optionally, you can add more actions after creating the approval and updating the task details. For example, you could add a Wait for an approval action to take the outcome of the approval request and perform conditional actions based on it. Or you could add an Update item action (SharePoint) to set the original request’s Approval status from Pending to Approved or Rejected. Or you could add a Send an email action (Outlook) to notify the requestor, copying the approver and HR, with the final outcome of the request.
Optional final steps ideas | Click to enlarge
Save your flow and test it.
That’s it! Now whenever a new request is created in SharePoint, a Planner task will be created for the approver with a direct link to the approval request.
You can apply this technique in other scenarios as well. For example, you could send chat messages or emails with links to approvals using Teams or Outlook actions. Or you could create personal To Do tasks with links using Microsoft To Do actions.
How might you be able to use direct links to specific approval requests in your business processes?
References and further reading
Looking for a deeper dive and more ideas? Look no further.
If you’re responsible for building flows in Power Automate, you’re certain to be asked to create an approval process at some point. This blog post will cover:
Comparison of the three approval action types, descriptions, and business use cases
How to create a basic approval flow using Power Automate
Dynamic content differences between Power Automate approval actions
Let’s start by comparing your three approval action options.
Comparison of Power Automate approval actions
One of the actions available in Power Automate is the Start and wait for an approval action. This action starts the approval process and waits for it to be completed before executing any additional actions. Actions that follow are typically response-dependent, such as creating an item or updating a status if approved or rejected.
Another action available in Power Automate is the Create an approval action. This action starts the approval process but does not wait for it to be completed. Instead, you can use the Wait for an approval action to wait for the approval to complete that was started by the Create an approval action. You might use these actions…
…if you want to have steps between creation and waiting. For example, if you wanted to customize the email that is sent to approvers, you would disable Enable notifications on the Create an approval step, then add a Send an email action afterwards but before the Wait for an approval step. This gives you complete control over the look and feel of the email request, rather than sticking to the default Power Automate branded message.
…if your approval process will take more than 30 days and your flow will time out before it’s finished. Create an approval creates the approval in Microsoft Teams (or Power Automate) and approvers can approve it there when they’re ready. Your flow won’t fail as You may not necessarily wait for an approval in the flow itself.
Here is a table that summarizes the differences between the various actions:
Action
Description
Business Use Case Example
Start and wait for an approval
Starts the approval process and waits for it to be completed.
A manager wants to automate the approval process for leave requests. They use the Start and wait for an approval action to ensure that the request is approved before the employee’s calendar is updated.
Create an approval
Starts the approval process but does not wait for it to be completed.
A team lead wants to automate the approval process for expense reports. They use the Create an approval action to create the approval record and send notifications, but they don’t want to wait for the approval to complete before executing the next step in the flow. In this case, the approval response may not affect the following steps, but just needed to be requested and logged.
Wait for an approval
Used to wait for an approval to complete that was started by the Create an approval action.
A project manager wants to automate the approval process for project proposals. They use the Create an approval action to create the approval record, send their own custom notifications as a Planner task, an email, or a chat message, and then use the Wait for an approval action to wait for the approval to complete before executing the next step(s) in the flow.
Create an approval and Wait for an approval can be used consecutively to achieve the same result as only using the all-in-one action of Start and wait for an approval. For example, let’s say you use Microsoft Teams to manage your team’s projects. You can use Power Automate to automate the approval process for project proposals. You can create a flow that uses the Create an approval action to create the approval record and send notifications to the approvers. Once the approvers have approved the proposal, you can use the Wait for an approval action to wait for the approval to complete before executing the next step in the flow. This ensures that the project proposal is approved before any additional actions are taken but also gives you the added benefits of flexibility down the road like adding steps between creation and waiting, as well as additional dynamic content that may be helpful (see the dynamic content section below).
How to create a basic approval flow using Power Automate
Here is a step-by-step guide for creating a basic approval flow in Power Automate using reimbursement requests as an example:
Select the When an item is created trigger for SharePoint. This trigger will start the flow when a new reimbursement request is created in the list.
Add the Start and wait for an approval action to your flow. This action will start the approval process and wait for it to be completed before executing any additional actions.
Configure the Start and wait for an approval action by specifying the approvers, the approval type, and any other relevant details. For example, you can specify that the approval should be sent to the employee’s manager and the Accounting department, and that the approval type should be Approve/Reject – Everyone must approve.
Add any additional actions that you want to execute after the approval process has been completed. You’ll almost always have a Condition control that checks to see if the response was Approve or Reject. Then, for example, you might use the Send an email action to notify the employee that their reimbursement request has been approved, and maybe Update item to set the SharePoint item’s status as Approved.
Here is a side-by-side comparison that shows the steps for a flow that uses start and wait for an approval, and a different one that shows using create an approval, send an email, then wait for an approval:
Start and wait for an approval
Create an approval, send an email, then wait for an approval
1. Add the Start and wait for an approval action to your flow.
1. Add the Create an approval action to your flow.
2. Configure the Start and wait for an approval action by specifying the approvers, the approval type, and any other relevant details.
2. Configure the Create an approval action by specifying the approvers, the approval type, and any other relevant details. In this example, we would disable the Enable notifications setting so we can send a custom notification.
3. Add any additional actions that you want to execute after the approval process has been completed such as a response-dependent (Condition control) secondary level of approvals.
3. Add the Send an email action to your flow to notify the requestor and/or approver(s) of the request details and action required.
4. Add the Wait for an approval action to your flow.
5. Configure the Wait for an approval action to wait for the approval to complete before executing any additional actions like a response-dependent (Condition control) status column update.
Table comparing the steps added to an approval flow using two different approaches
Not only do you use these approval actions in different scenarios, but your choice also affects the dynamic content you can use later in the flow. Let’s take a look at that next.
Dynamic content differences between Power Automate approval actions
The choices you make for which approval actions affect which dynamic content is available to you in later steps. Here’s an example of the dynamic content panel for a step following Create an approval:
A screenshot of selecting dynamic content from a Create an approval step | Click to enlarge
Here’s a listing of all the dynamic content alphabetically listed and which actions provide it for you.
Dynamic content
Description
Start and wait for an approval
Create an approval
Wait for an approval
Approval ID
The name of the approval
✓
✓
✓
Approvers
All of the approvers
Approvers Approver email
The email address of the approver
✓
Approvers Approver ID
The ID of the approver
✓
Approvers Approver name
The name of the approver
✓
Approvers Approver tenant ID
The tenant ID of the approver
✓
Approvers Approver user principal name
The principal name of the approver
✓
Approvers Item
✓
body
✓
✓
✓
Completion date
Date the approval was completed
✓
✓
Details
Additional details about the request
✓
✓
✓
Item link
A link to the item to approve
✓
✓
✓
Item link description
Description of the link to the item
✓
✓
✓
Outcome
The outcome of the approval
✓
✓
Request date
Date the approval request was sent
✓
✓
✓
Respond link
The link to respond to the approval
✓
Response summary
A summary of the responses
✓
✓
Responses
All of the responses
✓
✓
Responses Approver email
The email address of the approver
✓
✓
Responses Approver ID
The ID of the approver
✓
✓
Responses Approver name
The name of the approver
✓
✓
Responses Approver response
The response from the approver
✓
✓
Responses Approver tenant ID
The tenant ID of the approver
✓
✓
Responses Approver user principal name
The principal name of the approver
✓
✓
Responses Comments
Comments added by the approver
✓
✓
Responses Item
✓
✓
Responses Request date
Date the approval request was sent
✓
✓
Responses responder
✓
✓
Responses Response date
Date the approval response was sent
✓
✓
Teams Adaptive Card
An adaptive card that can be posted to users to respond from within Microsoft Teams
✓
Title
The title of the approval
✓
✓
✓
Table comparing dynamic content for different approval actions in Power Automate
One of the most valuable differences here, in my opinion, is the inclusion of Respond link. It’s only available for the Create an approval action. This allows you to send custom reminders with links that take users directly to the item(s) they still need to approve. You could also consider just sending users directly to the Approvals app in Microsoft Teams to put eyes on all their outstanding requests.
Conclusion
As you can see, a simple action choice comes with a lot of potential for creating rich processes. And with all of the options provided through dynamic content, we can customize the approval process quite a bit. In most cases, you’ll probably use Start and wait for an approval. But as you develop more flows, you may find yourself wanting a greater degree of customization and flexibility so you opt for the Create an approval + Wait for an approval approach.
What sort of approval processes are you working on automating with Power Automate? Let me know in the comments or on LinkedIn.
If you want to create a direct hyperlink in an email or chat message that takes a user directly to the Approvals app within Microsoft Teams, it’s luckily pretty straightforward. You might do this if you want to remind users to review any pending/open approvals on a regular basis, nudge a specific person to complete an approval, or create a custom approval request email for a Power Automate flow.
In this blog post I’ll highlight how you can get a direct link to Approvals for enterprise and GCC subscriptions in both Microsoft Teams and Power Automate.
How to create a direct link to the Approvals app in Microsoft Teams
To send users directly to the Approvals app in Microsoft Teams, your URL may be exactly the same as one of these. That’s right, no modification needed! That’s because the alphanumeric content in the URL is the app ID and it stays the same from one organization to the next.
However, the app ID does differ for different versions of the Approvals app. For instance:
Replace the alphanumeric id before /approvals with the app ID specific to your Approvals app
How to find your app ID
If neither of the examples above (normal Approvals or GCC Approvals) works for you, you may have a different Approvals app or the ID may have changed or been copied incorrectly. To find your app ID:
An app details page in the Microsoft Teams admin center | Click to enlarge
How to create a direct link to the Approvals page of Power Automate
If you prefer users complete approvals via the browser using Power Automate (same approvals, different interface), you may instead go to Power Automate in your browser and click on Approvals from the left navigation menu then copy that entire URL. It will be the same for all users in your organization.
You can, alternatively, copy one of my fake URLs above and replace everything between Default- and /approvals with your organization’s ID. To get this, visit Power Automate in your browser and copy the ID out of its URL.
Power Automate URL’s ID location | Click to enlarge
Microsoft Teams and Viva Engage (formerly known as Yammer) both empower communication and collaboration within an organization but they have different strengths and purposes. So how do you decide which one to use for your needs?
When I’m asked the question “when do I use which?”, I usually respond with another question: “Are you wanting to accomplish work together, or work on employee engagement and culture?” It’s not that you can’t do both with either tool – but each has its strength for different purposes. This post will help clarify when you might choose one over the other for various needs.
Feature comparison: Teams vs Viva Engage
To help you understand the differences between Microsoft Teams and Viva Engage, I’ve put together a comparison table that highlights their key concepts and strengths. I’ll go into more detail later in this post.
Feature
Microsoft Teams
Viva Engage
Communication
Chat, voice, and video calls
Community building, leadership engagement
Collaboration
File sharing, co-authoring, and real-time collaboration
Knowledge sharing, self-expression
Integration
Integrated with other Microsoft 365 apps
Integrated with other Microsoft 365 apps
Deployment
Managed by Teams admin
Managed by Teams admin
User Interface
Chat-based interface
Community-based interface
Use Cases
Real-time communication and collaboration
Community building and knowledge sharing
Table comparing core concepts and abilities of Microsoft Teams and Viva Engage
As you can see from the table, Microsoft Teams excels at real-time communication and collaboration, while Viva Engage is focused on community building and knowledge sharing. So when deciding which tool to use, it’s important to consider your goals and the needs of your team or organization.
Next, let’s look at another commonly asked question that gets deeper into each app – when I need a new place for my team/group, should I create a team in Microsoft Teams or a community in Viva Engage?
Teams vs communities: When to use which
You’re going to be at a crossroads occasionally when you need to establish a new group of people in one (or both) apps. While both apps allow you to create groups of people and share resources, they are best suited for different scenarios. So do you need a new team, or a new community?
Microsoft Teams: Real-time collaboration
In Microsoft Teams, you can create a team for real-time communication and collaboration. Teams are ideal for scenarios where you need to work on a project together, coordinate tasks, or share files. With features like chat, voice and video calls, and co-authoring, Microsoft Teams makes it easy to collaborate and get work done.
Viva Engage: Community building
In Viva Engage, you can create a community for knowledge sharing and community building. Communities are ideal for scenarios where you want to share best practices, discuss industry trends, or build a sense of community around a shared interest or goal. With features like community discussions, knowledge sharing, and leadership engagement, Viva Engage helps you foster a strong and engaged community as well as company culture.
Business use case comparison: Teams vs Viva Engage
The following table helps demonstrate when I, personally, would choose one app over the other. There is a great deal of personal preference here and there is no 100% correct answer for all organizations and scenarios. But I hope this helps you form your own decisions, nonetheless.
Business use case
Team
Community
Launch a new product and get feedback from customers and stakeholders
✓
✓
Organize a virtual live event with speakers, Q&A, and polls
✓*
✓
Coordinate a project with tasks, deadlines, and progress reports
✓
Share best practices and tips with peers in the same role or function
✓
Connect with leaders and experts and ask questions or share ideas
✓
Collaborate on a document or presentation with co-authors and reviewers
✓
Celebrate a team milestone or achievement with praise and recognition
✓
✓
Find relevant information and resources for a specific topic or domain
✓
Manage a sales pipeline and track leads, opportunities, and deals
✓
Communicate urgent updates and announcements to the whole organization
✓
Conduct a brainstorming session and generate new ideas or solutions
✓
Plan and execute a marketing campaign or a product launch
✓
Build a personal network and find people with common interests or goals
✓
Table comparing when to use a team (Microsoft Teams) vs a community (Viva Engage)
*I would choose Viva Engage over Microsoft Teams for most live events that are this interactive because the features being used imply engagement and broad communication. I lean toward Teams for smaller meetings, typically less produced, and more task oriented.
Summary
In summary, you might choose to create a team in Microsoft Teams when you need to collaborate and communicate in real-time, and you might choose to create a community in Viva Engage when you want to build and foster a community around a shared interest or goal. For more information on Viva Engage, you can check out the official Microsoft documentation.
What do you think? How do you use Microsoft Teams and Viva Engage in your organization? Share your comments below or reach out to me on LinkedIn.
You can continue learning and reading about Microsoft Teams and Viva Engage with these resources:
How can you empower your employees to connect and collaborate across the company, no matter where or when they work? The answer is Microsoft Viva Engage, the new and improved evolution of Yammer, that creates an inclusive and engaging employee experience for everyone. The Viva Engage app in Teams enables organizations to create community, foster engagement with leadership, access knowledge and answers, and develop personal networks.
The app details page for Viva Engage in Microsoft Teams | Click to enlarge
Viva Engage is powered by Yammer services, so you can access the same content and features in Yammer web, desktop, and mobile apps as well as in Teams.
In this blog post, we will share three user stories that illustrate how different employees use Viva Engage in different ways to accomplish their goals and work smarter.
User story 1: A frontline worker who uses Viva Engage to stay connected and informed
Maria is a retail associate at a large clothing store. She works on the shop floor, interacting with customers and managing inventory. She doesn’t have a dedicated desk or computer, so she relies on her smartphone to access Viva Engage in Teams.
Maria uses Viva Engage to:
Join and follow communities that are relevant to her role, such as the store community, the customer service community, and the product knowledge community.
Receive and respond to announcements from her manager and the corporate headquarters, such as new policies, promotions, and feedback surveys.
Ask and answer questions in the communities, using the Q&A feature to mark the best answers and upvote helpful replies.
Share stories and photos of her work and experience, using the storyline feature to create engaging posts that highlight her achievements and challenges.
Learn from her peers and experts, using the topics feature to follow hashtags and @mentions that interest her and help her improve her skills and knowledge.
Maria feels more connected and informed with Viva Engage. She can communicate and collaborate with her colleagues across the store and the company and access the information and resources she needs to do her job well and grow her career.
User story 2: A project manager who uses Viva Engage to manage and coordinate a cross-functional team
David is a project manager at a software company. He leads a team of developers, designers, testers, and marketers who work on a new product feature. He works remotely, so he uses Viva Engage in Teams to manage and coordinate his team.
David uses Viva Engage to:
Create and manage a community for his project team, where he can share updates, documents, and feedback with his team members and stakeholders.
Host and join virtual events in the community, using the live events feature to stream presentations, demos, and Q&A sessions with his team and the wider audience.
Interact with senior executives and thought leaders, using the leadership corner feature to view and join activities from top management, take polls, participate in hashtag campaigns and AMAs, and network with new leaders across the organization.
Crowdsource ideas and solutions, using the questions and answers feature to post and pin questions, upvote replies, and mark the best answers to solicit input and feedback from his team and the broader network.
Analyze and improve his community’s performance, using the analytics feature to get detailed insights into every community, event, and conversation, and take action to measure and increase activity and engagement.
David feels more productive and collaborative with Viva Engage. He can manage and coordinate his project team effectively and leverage the collective intelligence and experience of the organization to deliver better outcomes.
User story 3: A human resources manager who uses Viva Engage to foster a culture of diversity and inclusion
Lisa is a human resources manager at a manufacturing company. She is responsible for developing and implementing diversity and inclusion initiatives across the company. She works in the headquarters, but she travels frequently to visit different sites and regions. She uses Viva Engage in Teams to foster a culture of diversity and inclusion.
Lisa uses Viva Engage to:
Create and support employee resource groups (ERGs), using the communities feature to create and join communities for different affinity groups, such as women, LGBTQ+, veterans, and people with disabilities.
Launch and promote diversity and inclusion campaigns, using the community campaigns feature to create and manage organization-wide campaigns with dedicated campaign pages that aggregate posts from across the network into a unified view.
Share and celebrate stories of diversity and inclusion, using the storylines feature to create, upload, and share stories that highlight the diversity and inclusion achievements and challenges of the company and its employees.
Educate and empower employees on diversity and inclusion, using the learning feature to find and share relevant content from learning providers and company resources, and the live events feature to host and join webinars and workshops on diversity and inclusion topics.
Monitor and improve the diversity and inclusion outcomes, using the analytics feature to track and measure the impact of the diversity and inclusion initiatives, and the feedback feature to solicit and respond to employee suggestions and concerns.
Lisa feels more inspired and impactful with Viva Engage. She can foster a culture of diversity and inclusion across the company, and support and celebrate the diverse identities and perspectives of the employees.
Conclusion
These user stories show how Viva Engage helps employees connect and collaborate across the organization, regardless of their role, location, or background. Viva Engage is part of Microsoft Viva, the employee experience platform designed to help people connect, focus, learn, and thrive at work. Learn more about Viva here.
If you want to try Viva Engage for yourself, you can install the Viva Engage app in Teams and start creating and joining communities and conversations. You can also access Viva Engage in Yammer web, desktop, and mobile apps. For more information and guidance on how to use Viva Engage, check out the Microsoft Learn module here. And check out the introduction video here:
Power Automate allows you to automate workflows across various applications and services. However, when you create a flow, you need to decide how to authenticate and authorize it to access the data sources and actions it needs. This is where service principals and service accounts come in.
Service principals are special types of users that represent an Azure AD application. They have a system administrator role and use a client secret (a permanent password) to connect to data sources such as Dataverse. Service accounts are regular user accounts that have a username and password. They can be assigned different roles and licenses depending on the flow’s needs.
So which one should you use for your Power Automate flows: service principals or service accounts? Here are some pros and cons of each option:
Service Principals
Service Accounts
Pros:
Pros:
– More secure as they do not expose username or password
– Easier to set up and manage
– Do not consume a license as they use an application user account
– Can be assigned different roles and licenses for different flows
– Can perform actions on behalf of organization users who trigger the flow
– Can access more data sources and actions than service principals
Cons:
Cons:
– More complex to configure and troubleshoot
– Less secure as they expose username or password
– Limited to data sources that support Azure AD authentication
– Consume a license for each service account used in a flow
Table comparing the pros and cons of Service Principals and Service Accounts
As you can see, there is no definitive answer to which option is better for your Power Automate flows. It depends on your specific scenario, requirements, and preferences. However, some general guidelines are:
Use service principals if you want more security, less licensing costs, and more flexibility in performing actions on behalf of other users.
Use service accounts if you want more simplicity, more data source options, and more control over roles and licenses.
This post has explained the high-level differences between service principals and service accounts to consider when building flows in Power Automate. For more information, please refer to these resources:
Do you want to automate your workflows with Power Automate and make sure they can last for years to come? If so, you need to pay attention to how you share your flows and how you sign into the services that you use in them. Using your own user account may seem convenient, but it can also cause trouble if your account gets changed or deleted. In this post, I will show you two examples of what can go wrong when you use personal accounts in Power Automate flows and how to avoid them by using a service account instead.
Consider these two scenarios involving Power Automate flows that connect to different services:
Bob creates a flow that triggers when a new item is added to a SharePoint list and sends an email alert to his team. He uses his own user account to create the flow and does not share it with anyone else. A few months later, Bob quits his job and his account is disabled. The flow stops functioning because the connection is lost and no one can access or edit it. The team does not receive any email notifications and has to manually monitor the SharePoint list for new items.
Carol creates a similar flow as Bob but she shares it with her colleague Dave as a co-owner. However, she still uses her own user account to authenticate to some connectors or actions within the flow, such as sending emails from her Outlook account. A few months later, Carol resigns from her job and her account is deactivated. The flow still runs but some connectors or actions fail because they rely on Carol’s credentials. The team receives incomplete or erroneous email notifications.
These examples demonstrate the risks of using personal accounts in Power Automate flows. And both scenarios could have been avoided if Bob and Carol had used a service account to create their flows and connect to the various services used in the flow. You may end up with broken connections, failed actions, or loss of access otherwise.
So what exactly is a service account? A service account is a special user account that has a fixed license and does not belong to any individual person. Multiple users may know/share the credentials to use the account for building flows. You’ll treat it much like a user account as you provision a license for it then add it to teams, groups, and roles so that it can perform actions a normal user would.
By using a service account, you can make sure that your flows run reliably and securely no matter what happens in your organization or team. Just be careful, as with any shared security asset, not to share a service account’s credentials with too many flow makers. 2-3 users would be the max I would personally consider for redundancy as people take leave and the organization experiences turnover.
Tips for building sturdier flows in Power Automate by using service accounts
Create a dedicated service account with a fixed license and assign it the appropriate roles and permissions (site or team membership, shared mailbox member, security group member, etc.)
Consider creating multiple service accounts that have access to different environments, teams, sites, etc. to ensure you don’t have one service account with access to absolutely everything
Creating the flow
Use a service account to create the flow or
Use a service account to create the flow and share it with other users as co-owners for more convenient edit access or
Share a flow you have already created with the service account as a co-owner (co-owners keep flows after other co-owners leave an organization)
Use the service account to authenticate the connectors or actions that you use in your flows, such as SharePoint, Outlook, or Teams. If any single step’s connection belongs to an individual, there is risk that the step will fail if that person’s account is disabled or even if they have authentication issues.
Test your flows regularly and monitor their performance and status using the service account
Document your flows and their connections and keep track of any changes or updates using the service account
SharePoint is the leading digital workplace platform that lets you create, manage, and share content with your team and your audience (among many other abilities). One of the best features for everyday users when creating content in SharePoint is the ability to easily add web parts to your pages and news. Web parts are like building blocks that let you add different features and functions in a single context alongside other building blocks – for example, Documents next to instructional text or policy reminders for using the library.
But how do you choose the right web parts for your pages and news? Well, it depends on what you want to do and who you want to reach. You should pick web parts that help you achieve your goals and communicate your message clearly and effectively. You should also keep your page design simple and neat, using only the web parts that you really need.
The add web part dialog | Click to enlarge
Here are some of the best web parts to use when creating SharePoint pages and news:
Web Part
What it does
Highlighted content
Shows content that matches certain criteria or attributes, such as content type, location, custom metdata, or search term. I like this web part a lot because it gives me plenty of flexibility and helps me surface the right content when I need it.
News
Displays the latest news on your SharePoint page, and can include news from multiple sites as well.
Hero
Shows up to five items with images, text, and links to make them stand out. You can use it to add some flair and visual interest to your SharePoint page.
Events
Creates and shows events on your page. You can use it to share important dates, deadlines, meetings, or celebrations with your audience.
Quick links
Adds links to your page for easy access. You can use it to direct your audience to other pages, sites, or external resources that are relevant to your content.
People
Shows information about people on your page. You can use it to introduce your team members, collaborators, or contacts to your audience. You can also display their profile pictures, names, roles, and contact information.
Document library
Shows documents on your page. You can use it to upload or link to files that you want to share with your audience. You can set it to only show a specific view of a library to manage your space better (perhaps a view with minimal columns shown).
List
Displays a list from your site. This surfaces a view of a particular list as a web part. Consider using views that filter a person field to [Me] (the signed in user). This is a great way to personalize pages (your requests, your tasks, etc.) and surface relevant information alongside related resources (countdowns, calendars, files, policies, etc.).
File viewer
Shows files on your page. You can use it to display files such as videos, images, PDFs, or Microsoft 365 app files like Word, Excel, or PowerPoint files. You can also adjust the size and position of the file viewer on the page.
Embed
Shows content from other sites that allow embedding. You can use it to add content from sites like YouTube, Twitter, or Spotify to your page. You can also customize the appearance and behavior of the embedded content on the page.
Table of 10 SharePoint Online web parts to consider for your pages and news
Each web part can be customized to suit your needs and preferences. Ready to start building better pages? Check out this video, Create pages in SharePoint Online sites, to see the process:
Microsoft Teams is a powerful tool for teamwork and collaboration that has transformed the landscape of digital work. You can create and join teams (groups of people and their shared tools and work), chat with others within and beyond your organization, share and manage files, and much more. However, to make the most of Teams, you need to configure some settings and permissions for your team on a case-by-case basis. In this blog post, I will highlight five important settings to consider for each of your teams in Microsoft Teams.
Not a team owner (yet)? Share these topics with whoever is or keep them in mind for your future teams. I’ll cover:
Team name and description
Team privacy
Team members and owners
Team channels and tabs
Team notifications and mentions
1. Team name and description
The team name and description are the first things that people see when they browse or search for teams. They should be clear, concise, and informative. You can change the team name and description by going to the team name, clicking More options | Edit team, and typing in the new name and description.
Consider using a naming convention to make it clear which region, department, audience, etc. a team belongs to. For example, perhaps an EXT_ prefix will always preceed teams with external participants. Learn more about team naming conventions here: The Importance of a Teams Naming Convention | Microsoft Learn
Edit team name and description steps | Click to enlarge
You can also add a team picture to make your team more instantly recognizable.
Steps to modify the team picture | Click to enlarge
2. Team privacy
The team privacy determines who can see and join your team. You can choose from two options: public or private. A public team is visible to anyone in your organization, and anyone can join it without approval. A private team is only visible to team members, and people need to request to join it or be invited by a team owner. You can change the team privacy by going to the team name, clicking More options | Edit team, and selecting the privacy option.
Team privacy setting | Click to enlarge
3. Team members and owners
The team members and owners are the people who belong to your team. The team members can chat, share files, and participate in meetings. The team owners can manage the team settings and permissions, add or remove members, and delete the team. You can add or remove team members as well as promote or demote roles (i.e. from member to owner) by going to the team name, clicking More options | Manage team, and selecting the Members tab.
Members settings for a team in Microsoft Teams | Click to enlarge
4. Team channels and tabs
The team channels and tabs are the spaces where you can have conversations and access tools within your team. The team channels are typically organized by topics, projects, or departments. You can create standard channels that are open to everyone in the team, or private channels that are only accessible to a subset of team members. You can add or remove team channels by going to the team name, clicking More options | Add channel or More options | Manage team, and selecting the Channels tab. Note that the General channel comes with every team and cannot be deleted.
You can also edit individual channel names, descriptions, and whether or not it’s shown or hidden by clicking More options | Edit this channel.
The team tabs along the top of each channel are the shortcuts to your favorite apps and tools within a channel. You can add tabs for a Planner board, a Power BI dashboard, a OneNote notebook, and more. You can add or remove team tabs by going to a channel, clicking the + sign at the top, and choosing the app or tool you want to add.
The add a tab dialog where you can choose an app | Click to enlarge
You can also reorder the tabs by dragging and dropping them, or delete the tabs by selecting it’s dropdown arrow and choosing Remove.
5. Team notifications and mentions
The team notifications and mentions are two ways to stay updated and alert your team members. The team notifications are the alerts that you receive when something happens in your team, such as a new message, a new file, or a new meeting. You can customize your team notifications by going to Settings and more (…) and then Settings | Notifications, and choosing the notification level and sound for each activity.
Notification settings for the Microsoft Teams client app | Click to enlarge
The team mentions are the tags that you use to get someone’s attention in a conversation. You can mention a person, a channel, a tag, or the whole team by typing @ followed by their name. The team mentions help you communicate effectively and efficiently with your team.
You can also send a message as important, indicating visually that it’s a high priority.
Steps to mark a message as important in Microsoft Teams | Click to enlarge
Learn about more permissions and settings
There are, of course, many more than 5 settings to consider for each of your teams. While I have highlighted specific topics and considerations, I encourage you to keep learning with these resources:
