As we continuously strive to improve and unify our services, the SharePoint News connector will be retiring on July 22, 2024.
Starting July 22, 2024, we will stop the creation of new SharePoint News connectors in Microsoft Teams. Then existing SharePoint News connectors will be retired, and users will no longer receive new post notifications through this connector from August 26, 2024.
This article provides an overview of the deprecation timeline, its impact on customers, and alternative solutions.
Timelines
|
Date |
Action |
|---|---|
|
July 22, 2024 |
Creation of new SharePoint News connectors will no longer be possible. |
|
August 26, 2024 |
Existing SharePoint News connectors will be retired, and users will stop receiving new post notifications. |
Impact to Customers
Starting August 26, 2024, users will not be able to receive SharePoint site news notifications in Teams through the SharePoint News connector. This change will automatically occur by the specified date, and no admin action is required. However, it is important to notify your users about this change and update any relevant documentation.
How to identify if you have a configured SharePoint News Connector
-
In Teams, navigate to a Team channel.
-
Select the More channel options (...) and select Manage channel.
-
Under the Connectors section, select Edit.
-
Select Configured. If the SharePoint News Connector is configured, it will show up in the list.
Alternative Solutions
To continue receiving SharePoint site news notifications in Microsoft Teams channel, consider the following alternative solutions:
Viva Connections Notifications (Recommended if you already have Viva Connections set up and enabled in your org)
The Viva Connections app delivers News notifications via Microsoft Teams and links users to the Viva Connections app through the notification. Learn more about Viva Connections News notifications.
Viva Amplify (Recommended if you already have Viva Amplify set up and enabled in your org)
Viva Amplify brings together internal communication processes in a single tool. You create content once, then publish your message through SharePoint, email, Microsoft Teams, and soon Viva Engage
Create your own Workflow in Teams (Recommended if you do not have Viva Connections or Viva Amplify in your org). Follow the instructions below to learn how:
-
Install the Workflows app in Teams.
-
On the left pane in Teams, select Apps and then select Workflows.
-
Select the Create tab, and then select Create from blank in the top right.
-
On the new blank flow, start by configuring the trigger action. Search for SharePoint. Then choose the When a file is created or modified (properties only) trigger.
-
Next, choose a Site Address. In the Library Name field, select Enter Custom Value and manually type “Site Pages". Once done, select New Step.
-
Use the Condition control and select the Promoted State. Set the Promoted State equal to "2", which is the metadata for New Post published.
-
After setting the condition for the trigger, you will then set up the action for Yes. Search and select Microsoft Teams, choose Actions, and select Post message in a chat or channel.
-
Set up the message to be sent to the team and channel that you want. You can choose to post the message as a flow bot or as a user.
-
Save the Workflow.
Action Items for Admins
While no admin action is required to implement the deprecation, you should:
-
Notify your users about the upcoming changes.
-
Update any relevant internal documentation to reflect these changes.
-
Share the alternative solutions with your users to ensure a smooth transition.
