sp-dev-fx-webparts/samples/react-teams-message-user
Hugo Bernier 103907bdc6 Added compatibility warning on readme and template 2023-02-10 10:22:32 -05:00
..
assets Changed docs links to learn 2022-10-24 09:42:45 -04:00
config Commit the webpart sample 2021-02-28 16:12:24 +00:00
src Updated readme 2021-02-28 13:07:00 -05:00
.editorconfig Commit the webpart sample 2021-02-28 16:12:24 +00:00
.gitignore Commit the webpart sample 2021-02-28 16:12:24 +00:00
.yo-rc.json Commit the webpart sample 2021-02-28 16:12:24 +00:00
README.md Added compatibility warning on readme and template 2023-02-10 10:22:32 -05:00
gulpfile.js Commit the webpart sample 2021-02-28 16:12:24 +00:00
package-lock.json Commit the webpart sample 2021-02-28 16:12:24 +00:00
package.json Commit the webpart sample 2021-02-28 16:12:24 +00:00
tsconfig.json Commit the webpart sample 2021-02-28 16:12:24 +00:00
tslint.json Commit the webpart sample 2021-02-28 16:12:24 +00:00

README.md

Message Teams User

Summary

Sample that shows how to send a message to Microsoft Teams using a SharePoint framework solution using Microsoft Graph.

Message Teams Web part preview.

Compatibility

⚠️ Important
Every SPFx version is only compatible with specific version(s) of Node.js. In order to be able to build this sample, please ensure that the version of Node on your workstation matches one of the versions listed in this section. This sample will not work on a different version of Node.
Refer to https://aka.ms/spfx-matrix for more information on SPFx compatibility.

SPFx 1.11 Node.js v10 Compatible with SharePoint Online Does not work with SharePoint 2019 Does not work with SharePoint 2016 (Feature Pack 2) Teams Incompatible Local Workbench Incompatible Hosted Workbench Compatible Compatible with Remote Containers

Applies to

Prerequisites

  • SharePoint Online tenant
  • You have provided permission in SharePoint admin for accessing Graph API on behalf of your solution. We can do it before deployment as proactive steps, or after deployment. You can refer to steps about how to do this post-deployment. Basically you have to use API Access Page of SharePoint admin and add below permission for our use case.
 "webApiPermissionRequests": [
  {
    "resource": "Microsoft Graph",
    "scope": "ChatMessage.Send"
  },
  {
    "resource": "Microsoft Graph",
    "scope": "Chat.Create"
  },
  {
    "resource": "Microsoft Graph",
    "scope": "Chat.ReadWrite" 
  },
  {
    "resource": "Microsoft Graph",
    "scope": "User.Read"
  },
  {
    "resource": "Microsoft Graph",
    "scope": "User.ReadWrite.All"
  },
  {
    "resource": "Microsoft Graph",
    "scope": "Directory.Read.All"
  },
  {
    "resource": "Microsoft Graph",
    "scope": "Directory.ReadWrite.All"
  }
]

Concepts

This Web Part illustrates the following concepts on top of the SharePoint Framework:

  • Using react framework in SPFx web part
  • Calling Microsoft Graph API in SPFx web part

Solution

Solution Author(s)
teams-messages David Ramalho (@davRamalho)

Version history

Version Date Comments
1.0 February 28, 2021 Initial release

Minimal Path to Awesome

  • Clone this repository
  • in the command line run:
    • npm install
    • gulp serve

This sample can also be opened with VS Code Remote Development. Visit https://aka.ms/spfx-devcontainer for further instructions.

Help

We do not support samples, but we this community is always willing to help, and we want to improve these samples. We use GitHub to track issues, which makes it easy for community members to volunteer their time and help resolve issues.

If you're having issues building the solution, please run spfx doctor from within the solution folder to diagnose incompatibility issues with your environment.

If you encounter any issues while using this sample, create a new issue.

For questions regarding this sample, create a new question.

Finally, if you have an idea for improvement, make a suggestion.

Disclaimer

THIS CODE IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR NON-INFRINGEMENT.