Category: Microsoft Teams

  • Streamline the employee onboarding journey

    Streamline the employee onboarding journey

    Welcome to the era of digital employee onboarding! In today’s remote, or hybrid working landscape, it’s crucial to have a seamless and engaging onboarding process for your new hires. Say goodbye to traditional onboarding programs and embrace the power of digital solutions.

    With Microsoft Teams, you can create an easily accessible and efficient digital onboarding experience. In this article, we’ll explore the benefits of digital onboarding, and showcase how Microsoft Teams can transform your onboarding programs.

    On-site, Hybrid, or Remote Working – Digital Onboarding is the way to go

    Digital employee onboarding offers scalability and flexibility, no matter if your new hires are starting in the office or remote working.

    Remote and hybrid working has become the norm, and digital employee onboarding is the key to success. Embrace the flexibility and scalability of remote work by utilizing digital processes. Leave behind the hassles of traditional onboarding and welcome new hires with open arms through a digital onboarding experience. Offer them easy access to information, resources, and tools necessary for a smooth transition.

    Digital onboarding solutions streamline the way you welcome new team members. Simplify administrative tasks and make the onboarding process a breeze. Say goodbye to stacks of paperwork with digital offer letters and contracts. Create a digital onboarding process with digital onboarding checklists that guide new hires through essential tasks. Boost employee engagement with interactive training materials, fostering a positive digital onboarding experience. These digital processes enhance efficiency and create a seamless

    Microsoft Teams: Your Digital Onboarding Ally

    Microsoft Teams is the ultimate tool for transforming your digital employee onboarding process. It provides an all-in-one platform for communication, collaboration, and knowledge sharing.

    When used to its full potential, Microsoft Teams can become a truly powerful onboarding platform.

    When onboarding new hires, many players are involved, including the IT team, the HR department, and the hiring manager. The responsibility for kicking off the digital onboarding process often falls on the shoulders of the IT team, but should it?

    With the help of advanced Microsoft Teams templates and a well-defined Teams provisioning and approval process, it doesn’t have to. Harness the potential of Microsoft Teams templates designed specifically for onboarding new employees to jumpstart your digital onboarding program.

    A Team template pre-built by your IT team can come with pre-built channels, tabs, documents, links, and integrations. Using the new team the new hires can connect with their team members, ask questions, and access important resources. The HR rep or the hiring manager can create a new Team from a template when the digital onboarding process is started.

  • The five benefits of content types in SharePoint and Teams

    The five benefits of content types in SharePoint and Teams

    SharePoint Online (and its stablemate Teams) is a powerful platform for document management, collaboration, and content sharing within organizations, especially when it’s properly governed. One of its standout features is content types, which offer a structured way to manage and organize documents, images, list items and other files. In this post, we’ll explore the 5 key benefits of using content types in SharePoint Online and Teams and delve into the details of each one.

    1 – Create consistency

    Content types allow you to define a specific template structure and metadata and for documents, forms, images or list items. By using templates, you can ensure that every piece of content created is based on a predefined, approved foundation, reducing the chances of errors or data inconsistencies.

    • ‍Metadata – By attaching metadata columns to content types, you can ensure that critical information like category, department, or client is consistently applied to relevant content.
    • Document templates – Content types can be associated with MS Office document templates (Word, Excel, PowerPoint), ensuring that each document created from that content type starts with the same format and structure.

    2 – Improve search and discoverability

    SharePoint’s search capabilities are enhanced when content types are used. Content types make it easier to categorize and classify documents, making them more searchable and discoverable by users.

    • Custom metadata – You can add custom metadata fields to content types, allowing users to filter and search for content based on specific criteria, such as document type, project name, or client.
    • Managed metadata – Content types can be associated with managed metadata, creating a hierarchical structure that helps users navigate and find content more efficiently.
    • Search schema – Content types can be added to search schema that allow users to search for content across your organization with a particular content type.

    3 – Streamline your workflows

    Content types can be integrated into Power Automate workflows, making it easier to automate business processes and document approvals. This streamlines operations, saving time and reducing errors. For example:

    • Document approval – By defining a content type for approval documents, you can create a workflow that automatically routes documents for review and approval to the appropriate individuals or teams based on selection of say a category, client or product type.
    • Document retention – Content types can be used to enforce retention policies, ensuring that specifically categorized documents are archived or deleted according to compliance requirements.

    4 – Simplify your content management

    Content types simplify content management by enabling you to organize and classify documents logically. This enhances the user experience and reduces the learning curve for new team members.

    Folderless document libraries

    The use of content types allows for folderless document libraries, where content is organized into views based on the metadata each file is associated with and the content types themselves. This means that instead of navigating through a complex folder structure, users can filter and sort content based on content types and their associated metadata.

    Content type hub

    In SharePoint Online, you can create and manage and publish content types directly from the SharePoint Admin Center. By doing this centrally, you can use the same set of columns across multiple content types and use the same content type in multiple locations in your tenant, reducing data inconsistency.

    For example, one department may refer to a document as a Standard Operating Procedure whilst another exclusively uses the term SOP. By reusing the same column for both departments, you can standardize the term used when adding the metadata for SOPs, improving searchability of your content.

    5 – Add scalability and future-proofing

    As your organization grows and evolves, content types provide the flexibility to adapt to changing needs and requirements. They offer a scalable solution for content management.

    ‍Easy updates

    If you need to modify metadata or document templates, you can update the content type centrally in the content type hub, and the changes will propagate to all associated content across your SharePoint environment, reducing the number of times that you need to make the change.

    Reusability

    Content types can be reused across multiple site collections and sites, reducing duplication efforts and ensuring that changes are applied consistently.

    In conclusion, content types in SharePoint Online offer a wide range of benefits, from maintaining consistency and improving search to streamlining workflows and simplifying content management. By harnessing the power of content types, organizations can enhance productivity, reduce errors, and adapt to changing business needs more effectively.

    Customization

    Whilst content types offer an effective way to standardize the metadata and document templates used, they still allow some flexibility and customization when needed. You can achieve this in two ways:

    1. Parent and child content types – When crafting a content type, you must designate an existing content type as the foundation for the new one. Your freshly created child content type then inherits all attributes from the chosen parent, allowing you to introduce additional customizations. This is useful in the case of content which has unique information that needs to be stored for a particular department, but still needs to have base organization-wide categorization.
    2. Content type instances – Once a content type has been deployed to a list or library, it’s possible to customize the columns available on that specific list or library by changing things such as the default selection of a choice column or adding an additional piece of metadata for capture.

    Final Considerations

    Structured vs unstructured content

    While content types serve as a robust tool for crafting organized and precisely defined content, they may not always align with every scenario. Before implementing content types, it’s a good idea to assess your content and categorize it into structured and unstructured segments.

    The unstructured segments provide flexibility for content creation and manipulation, enabling your users to operate in a manner they find most effective. These unstructured spaces often serve as initial points from which teams can then establish the need for structured content and associated workflow processes.

    Structured content will often require a more formal business process and will be easier to define with a few key pieces of metadata.

    Planning and collaboration

    To implement content types successfully, you will need to work closely with the users that the content types will affect. This will help you to define the metadata required for the content type accurately and also give the users themselves a chance to understand the why and the how of the structure being implemented.

    Incomplete or inaccurate data is worse than unstructured data. When structured areas are not logical or easy to work with, users will often revert to saving content in other areas, such as their OneDrive or desktop.

  • Creating a Breakout Room in Microsoft Teams

    Creating a Breakout Room in Microsoft Teams

    Breakout rooms are functionality that Microsoft has announced will be add to Teams by the end of 2020.

    What is a Breakout Room?

    Breakout Rooms and Breakout sessions allow members of large meeting to be broken into smaller groups. A great use-case for would be a training session (where you could divide the the audience in into smaller teams to work on an exercise)

    Breakout Rooms could also be used for planning workshops, requirements gathering, org-wide training, etc.

    Creating a Breakout Room

    1. Create your team

    If you are reading this, we’ll make the assumption that you know how to create a team

    2. Add a channel for each Microsoft Teams Breakout Room (once again, we assume that you know how to create a channel)

    Give each channel a relevant name to correspond to your Breakout groups. This could be subject-related or simply numbered so that you can let your attendees know which Breakout group they need to be joining. 

    At this point, you can choose to allow all the members of your main Teams team access to every channel / Breakout group, or you can choose the “Private –  Accessible only to a specific group of people with the team“. It depends on how much you want to control your audience’s ability to join each Breakout room and your particular use-case as to which option works best for you. Sometimes locking it down in this way can help remove the confusion of the audience knowing which Breakout meeting they are supposed to join as they will only be able to see the one they can access.

    You should then have your Team with the correct number of Channels to match how many breakout groups you need; in this example, we have 3.

    Step 3:  Start your Main meeting from the Team

    The main meeting can be started from the General channel of the Team, in the normal way.

    This could either be a scheduled call or a Meet now call. Both can be initiated by selecting the camera icon below the new conversation box:

    Start the meeting, from this point onwards, even when you start going into the Breakout sessions via the Channels, do not close the meeting until the entire session is over.

    If you navigate back to the Team by clicking on ‘Teams’ in the left-hand panel, you will see a camera icon next to the General tab and the meeting in the Conversation feed, indicating the main meeting is underway.

    At this stage, you could also start the Breakout channel meetings so you are ready for the Breakout sessions to start, or you can wait until they are needed during your session. 

    Step 4: Creating each Breakout Room meeting

    Once you are ready to open the breakout rooms, navigate to each of the channels in turn, by clicking ‘Teams’ on the right hand panel, selecting your team and then selecting the chanel. Using the ‘Meet Now’ Option in each channels conversation feed, start a meeting for each one. Remember to keep the main meeting open as you do this (don’t press the red button to close the meetings now until your whole session is over.)

    Each time you open a new meeting, you will need to navigate back to the main Team and select the next channel to open the next one. 

    Finally, as you navigate back to the Team you will notice that each channel now has a camera icon next to it, and that you have a list of meetings in the top left showing that some are on hold and you are in one of them.

    If you now select the play button next to the “General” meeting and select the meeting preview to go full screen, you will be back in the main General meeting and are now ready to go. 

    You will also notice that from this main meeting, you can see each of your other meetings on hold. You can visit each one as and when you want to, simply by clicking the triangle play button. You can drop in and out as often as you wish.

    Step 5: Breakout work and back to Main Meeting

    Now instruct your students or attendees to go and join the meeting in their relevant channel (allocated breakout session) in this team. To do this they can navigate to the channel via the left-hand panel by clicking ‘Teams’, select the Team, click on the Breakout room / Teams Channel you have allocated or instructed them to go to. Then they should be able to join the meeting by clicking ‘Join’ button in the conversation feed:

    As the Breakout sessions and group collaboration progress in each of the Channel meeting rooms, you as the person running the session can jump between each meeting to help out and check on progress simply by clicking the triangle play button on each meeting bar in turn.

    Once the Breakout sessions are complete, you can ask your attendees to leave their Breakout meetings by clicking the red hangup button in the meeting and to rejoin the main meeting in the General Channel. It’s best to Instruct them all that if they lose the meeting they can easily get back to it by going to the General Channel and clicking on ‘Join meeting’.

    Here is a great you tube video from a well known Microsoft expert called Kevin Stratvert, demonstrating how to to do this, I hope this helps:https://www.youtube.com/embed/d_iD5PLgr08?rel=0&modestbranding=0&controls=1&showinfo=1&fs=1&wmode=transparent

    There we have it, Breakout rooms in a Teams Meeting using the standard functionality.

    Microsoft are working on more Breakout room-specific functionality, although it is not clear yet on when that will be available.  Take a look at this user voice  – https://microsoftteams.uservoice.com/forums/555103-public/suggestions/35000044-introduce-breakout-room-functionality

    Hopefully, we will soon be able to update this post with a more structured way of achieving this, in the meantime, I hope this can help you.

  • Create a PnP template from a Microsoft Team

    Create a PnP template from a Microsoft Team

    What if you could extract Microsoft Teams team similar to SharePoint sites? Well, with the September 2020 release of the PnP Sites core nuget package it is now possible to extract a Microsoft Teams team as a PnP template.

    This is super awesome great news for folks who want use a templated experience to provision teams in the tenant or even across tenants.

    With this release, we will be able to export a Microsoft Teams team and its associated artefacts such as its settings (like discovery settings, guest settings, fun settings, members settings and messaging settings), team owners and members, team channels with their tabs configuration, apps installed in the particular team and even the team messages.

    So, how do you do that ? You can use your favourite PnP PowerShell or use the PnP Site core nuget package for C# implementation.

    To extract a Team using PnP PowerShell, you need to know the SharePoint URL of the Team.

    You can find that out if you go to your Teams > General channel > Files tab and then click Open in SharePoint. The URL would be something like (https://your-tenant.sharepoint.com/sites/HRTeam).

    Once you know the URL of the site, you should create a JSON file as below:https://d-35078493753717980787.ampproject.net/2009112034002/frame.html

    In the above JSON, if you set includeMessages attribute to true, it will also extract Teams messages but will slow down the extraction if there are a lot of messages. This doesn’t work in app-only scenarios.

    Also, you can set the includeGroupId attribute to true if you want to re-use the GroupId somewhere else in the provisioning process or store it for other purposes.

    After creating the JSON file, open PnP PowerShell and execute the following commands. You need to be a very privileged user (mostly a Global admin) to execute these commands.
    https://d-35078493753717980787.ampproject.net/2009112034002/frame.html


    In the above commands, we are using a fantastic PnP PowerShell capability to create an Azure AD app with App-only permissions. This will also create a certificate and upload it in the app for you to use later on to connect to SharePoint and Graph.

    To do similar thing in CSOM C#, you can do that as below:
    https://d-35078493753717980787.ampproject.net/2009112034002/frame.html

    Using this approach, you can extract a Microsoft Teams team and save it as a template which you can then edit and modify as per your requirement.

    Now that you have extracted the template, modify it if you want to change some stuff in the template. You can then apply it using the Apply-PnPTenantTemplate command or the equivalent in CSOM C# which is tenant.ApplyTenantTemplate() method. You can read more about if you want to in my blog here.

    End result if all goes well, will be a Teams PnP Template somewhat similar as mentioned below:

    PS:

    1) You need to use the latest version ( September 2020 or later) of PnP PowerShell and PnP Sites core to extract MS Teams team as template.

    2) There seems to be some issue with the engine with regards to extracting some teams settings but you can modify them after extraction manually.

    3) There is also another attribute, includeAllTeams ,in the schema which if you specify to true will extract all the Teams in the tenant. This is a very time consuming process, so be careful before setting that. By default, it is false.

    4) If you want to extract multiple teams, then just add those team’s SharePoint URLs in the teamSiteUrls attribute separated by comma as below:

    "teamSiteUrls": ["https://<tenant>.sharepoint.com/sites/HRTeam","https://<tenant>.sharepoint.com/sites/ITTeam","https://<tenant>.sharepoint.com/sites/PRTeam"],

    This will extract the multiple teams in the same template.

    5) IMHO, this a great way to extract teams and store the templates so that we can provision them subsequently in a standard manner as per organization’s policies and standards. Also, helpful to store them in repository for maintainance and versioning purposes.

    6) Also, quite handy if you already have a webjob , azure functions which are triggered from SPFx or Flow or PowerApps for SharePoint sites provisioning which you can then extend it for teams with some changes. In these scenarios, be careful about the credentials, would suggest that you store them securely in Key Vault or encrypted database.

    7) In case daemon applications which won’t have popups for admin consent. you would need to use certificate authentication. For that, you can use Initialize-PnPPowerShellAuthentication command to create and upload the certificate. If you already have an Azure AD app with necessary permissions and certificates, you can use the Certificate and Thumbprint parameters in Connect-PnPOnline command.

    8) Now you might be wondering, how can I combine this with my SharePoint site collection which also has its own customizations like lists, content types etc. ?

    Well you can extract the SharePoint site collection separately using the Get-PnPProvisioningTemplate and then create a combined template by using the PnP Sequence elements. You can read more about this in this excellent blog written by Paolo Pialorsi . This will provision the Microsoft Teams and SharePoint site collection at once with all your customizations in place.

    9) Also, if you using App-only authentication to apply the teams template, you will not be able to post messages as that capability is not available AFAIK via Graph API which is used by the provisioning engine.

    PPS:

    This capability is extremely useful for creating Teams in a templated manner. But it is also a major concern as well now because admins will be able to extract and read teams messages (think Snowden, WikiLeaks etc.), so be very very careful with who has access to this capability. Very important to store these in a secure manner in your version control system.

    References –

    1) Initialize-PnPPowerShellAuthentication

    2) Get-PnPTenantTemplate

    Links –

    1. PnP PowerShell –PnP September 2020 Release

    2. PnP Sites Core nuget packge – SharePointPnPCoreOnline

    3. PnP Schema – Configuring the PnP Provisioning Engine

  • Employee recruitment and on-boarding with Office 365 and Power Platform – Pt 1

    Employee recruitment and on-boarding with Office 365 and Power Platform – Pt 1

    In the series of posts, we are going to look at how you can utilise the suite of Office 365 and Power Platform products to automate the recruitment and onboarding of new employees. We will use (among other things) SharePoint Online, Microsoft Teams, PowerApps, Power Automate, Word, Outlook and Power BI.

    We’ll also apply some JSON to format columns and create adaptive cards

    The scenario

    In this scenario, we will start with a request to recruit a new employee, which will then go through an approval process and trigger a series of actions within Power Automate flows.

    During this series, we’ll also create a Microsoft Team to store all details of applications and supporting documents (resumes, cover letters, etc.)

    Request to recruit

    To begin with, we’ll create a SharePoint team site (mine is called People Culture Team). In this site, we’ll create list (mine is called Recruitment Requests). My list has the following columns:

    NameType of column
    TitleSingle line of text
    Type of requestChoice
    (choices are ‘backfill’ & ‘new position’
    Position TitleSingle line of text
    New Position JustificationMultiple lines of text
    Previous Incumbent NameSingle line of text
    Previous Incumbent Reason For LeavingChoice
    (choices are ‘Internal Transfer’ & ‘Termination (including resignation’
    Covered By BudgetYes/No
    Request LocationChoice (for this example, you only need to have two or three choice. In real-life/larger company, you may prefer a lookup column)
    Reports ToPerson or Group
    Reports To PositionSingle line of text
    Employment TypeChoice (My choices are ‘Full-time’, ‘Part-time’, ‘Casual’ & ‘Fixed-term contract’
    Recruitment MethodChoice (My choices are ‘External’ & ‘Internal’)
    Commencement DateDate and time (Date only)
    Position Description AttachedYes/No
    Base SalaryCurrency
    SuperCurrency (might not apply to any readers outside of Australia)
    Mobile AllowanceCurrency
    Laptop AllowanceCurrency
    Link To RequestSingle line of text (we will use JSON to format this column in a later post)
    P&C ApproverPerson or group
    P&C OutcomeSingle line of text
    P&C CommentsMultiple lines of text
    SLT ApproverPerson or group
    SLT OutcomeSingle line of text
    SLT CommentsMultiple lines of text
    GM ApproverPerson or group
    GM OutcomeSingle line of text
    GM CommentsMultiple lines of text

    If you don’t want to manually create this list, here’s a flow I created for you. You just need to change the URL to one that sits inside your tenant, e.g. https://yourtenant.sharepoint.com/sites/peoplecultureteam, and run the flow.

  • Trigger a Power Automate flow from a Microsoft Teams message

    Trigger a Power Automate flow from a Microsoft Teams message

    Microsoft Teams can help bridge geographic and organizational gaps through capabilities like chat, meetings, and calling, but users often ask how it can help streamline the work they do. Fortunately, Teams and Microsoft Power Automate work seamlessly together to simplify how you and your team work.

    We’re excited to share a new way to use this integration to automate and simplify work, starting from a conversation in Teams.  The new “for a selected message” trigger enables any Teams user to create a custom message action to start a flow from any message in Teams.  Even more powerful, is that flow creators can build this capability for their entire team, so everyone can easily benefit from some automation in their workday.

    Example scenarios:

    Below are four great examples of how teams can automate critical processes right from chat, but thanks to the flexibility of Power Automate, the possibilities are endless. Each of these flows are available as templates for you to use or modify to fit your needs right away!

    Set a message reminder

    There are times you might want to be reminded of a message from a colleague or your manager at a later time, like after your Teams meeting, or before the next upcoming meeting in a week.  With a “follow-up later” flow, Teams users will simply have to click the “…” on the right-hand side of a message to set a reminder and specify when they want to be reminded.  The Flow bot will send a reminder and a link to the message right in Teams.

    Create a SharePoint item

    We all need to keep lists – whether that’s a store inventory, project status, or the plan for an event.  SharePoint lists are a great way to organize information and rich file types for you and your team, and now Teams users can easily add content to their SharePoint lists directly from chat with this new Power Automate trigger.  Once the flow laid out below has been created, users will be able to add critical data to their list right from the chat – for example, if they learn that new inventory has been received.

    Sales teams: Convert a chat to a Sales opportunity

    Creating a customer opportunity is a critical step in any Sales process, and often that opportunity starts with a conversation.  So why not capture that information right from that conversation where it began.

    When you build the flow below using the “for a selected message” trigger, anyone in your team can easily create a sales opportunity just by clicking the “…” on the right side of a message in Teams and selecting “Create a Sales opportunity”.  Simply fill out a custom form right in Teams, and the information you enter is automatically sent to your CRM system.

    Create a work item in Azure DevOps

    With so much collaboration and planning happening over chat now, messages can be a great way to request or report new work items to your development team. By combining the “for selected message” trigger with the Azure DevOps “create a work item” action, you can now use the message as the starting point to create a work item. All the details from the message, such as the message contents or who the sender was can be used to provide more details as part of creating the work item.

    These templates are just scratching the surface you can always create your own to fit your business needs. Check out below for specific instructions on creating custom message actions for Teams, and check back here often for updates on what we’re rolling out next!

    Creating your own Teams actions

    To create a custom Teams message flow, choose the “For a selected message” trigger from the Teams connector. You can even configure the trigger to collect information from the user when its run from within Teams. For instance, if the flow is creating a task, you can use the adaptive card to collect information like the title of the task and the description.

    Collecting information from the user

    To collect information as part of the flow, you can quickly and easily create a custom form right from within the flow editor using the embedded card designer experience.

    Using message details within the flow

    There are a number of message elements that are available as a trigger output for use within the flow. Some of the more useful properties include:

    • Message content – The full HTML content of the Teams message
    • Plain text message output – Plain text variation of the Teams message
    • Link to message – A direct url to reference the message
    • Sender display name, Sender id – Details of the user who sent the message
    • Originating user display name, Originating user id – Details of the user who invoked the flow

    Triggering the flow from within Teams

    Any flow that uses the “For a selected message” trigger shows up as a message action in the Teams message over flow “More actions” menu. The name that you give the flow is what is shown in the Teams client.

    Check out the “for a selected message” documentation to learn more about this new capability.  Of course the examples above are just scratching the surface of what is possible for you and your team to automate, so check out the Power Automate templates for Teams and learn to build your own flows to achieve even more.  We’re excited to hear about what you build!

  • @ mentioning people in Microsoft Teams with Power Automate

    @ mentioning people in Microsoft Teams with Power Automate

    Introduction

    Users have long been able to use the ‘send a message in Teams’ action but, unless people checked every channel of every team they wouldn’t know about the post.

    Now though, the Team bot can post a message AND notify the tagged user, so they know there is a message to read.

    In this post, I’m going to show you how to assign a task to a user and then notify the assignee, through the ‘Post a message as the Flow bot to a channel’ action (currently in preview).

    Prerequisites

    I’m going to assume that you have a basic working knowledge of Flow, SharePoint and Teams.

    Before we start, you’ll need a SharePoint list (using the modern experience), with the following columns:

    • Title
    • Description
    • Assigned to
    • Due date
    • Status

    And, of course, you’ll need an account for Microsoft Flow and a Microsoft Team to post to.

    Building the Flow

    1. Log into SharePoint and access your list and select Flow > Create a flow.

    2. From the dialog, select ‘Post message to Microsoft Teams for a selected item’.

    3. Select more and then select ‘Complete a custom action for the selected item’.

    4. Flow will open in a new tab (you may need to connect Flow to SharePoint and there is more information here).

    5. Select ‘Continue’.

    6. Give the flow a name and select save.

    7. Delete the text input

    8. Next, add a new action by selecting the new step button.

    9. Enter ‘Teams’ in the search box and select the Microsoft Teams icon.

    10. Select the Post a message as the Flow bot to a channel (preview) 

    11. Select the Team and Channel that you want to post to and then it’s time to create your message.

    Creating the message

    To get @mention to work, you only need to use a simple line of code, but I’m going to add a little bit of detail so that the mentioned user has something to read.

    1. In the message field, type <at></at> and place your cursor between the > and the <.

    2. In the dynamic content search box, select ‘Assigned to Email’.

    3. The assignee’s email address will be placed between the opening and closing tags

    4. Now the flow is configured to notify a user that they have a new message to read but, as I said, I’ll add more task information for context.

    Note: I’ve also used some basic HTML to format the message to make it more readable. You can read more about HTML here

    5. Now, you can return to your list and test your flow.

    6. If you haven’t already done so, create a task and assign to yourself.

    7. Select the task > Flow > your flow (in my case it’s ‘Post to Teams with @’).

    8. Select ‘Run flow’.

    9. You’ll receive a desktop notification.

    10. Open the Teams channel and view your message.

    Conclusion

    In this article, we have looked at how to use the Post to Microsoft Teams as the team bot action to post a message in Teams and alert a user. We did this by creating a manually triggered flow on a list, notifying the assignee of the task.