44
Hello everybody, I'm trying to build a manual flow to change my status message in MS Teams.
I based the flow on this 2 posts:
https://myteamsday.com/2021/09/22/setpresence/
https://www.damobird365.com/teams-status-update-via-power-automate/
However, my flow stucks during execution and never ends.
This is my flow:
and this is an example of execution:
(I waited until 5 minutes, then I stopped it).
Could anyone explain to me what is wrong or why flow stucks, please?
Thank you all!
I don't use this feature in production, but I have successfully tested it this year. I assume that its going to just stop working for everyone at some point. As far as I am aware, Microsoft Teams has deprecated the use of the forceAvailability property in favor of the Microsoft Graph REST API to set the state of a user’s presence session as an application. Presence sessions are used to set the user’s presence status in Teams. You can set the state of a user’s presence session using the setPresence method. https://learn.microsoft.com/en-us/power-platform/important-changes-coming
Does this code for "https://presence.teams.microsoft.com" still work for everyone? I keep getting a failure when I run the flow.
Effectively, using only message field in body request was succesfully: message expiration is automatically set to 01/01/10000
For me it's satisfying for now: thank you so much @Expiscornovus !
Hi @Gilgamesh,
A couple of questions:
1. Can you share a screenshot of the configuration of the Send an HTTP request to SharePoint action from your latest test?
2. Can you test it without the expiry property. Please try something like below in the body of the PUT request for the publishnote method
Share
Report
All responses (
Answers (
{
"message": "Only update the message"
}
Btw, I have just tested it myself in one my tenants which is located in EMEA region. I wasn't able to reproduce it, I can use the same site address for presence without any issues.
Hi @Gilgamesh,
Just to double check. You tried something like below?
And where is your tenant located? Like Damien mentioned in his blogpost the presence endpoint might have a different address when it is in the US.
Thank you for your reply, @Expiscornovus , but I've added Bearer in HTTP request, after trying without.
If I not add bearer, I get this error:
{"message":"The request is invalid.","modelState":{"$type":"System.Web.Http.HttpError, System.Web.Http","incomingNote.expiry":{"$type":"System.String[], System.Private.CoreLib","$values":["An error has occurred."]}}}
clientRequestId: 34a161...
Hi @Gilgamesh,
In both examples they are not using a Bearer token but just using the connection of the Send an HTTP request action. The action itself should work without the Bearer token.
Can you remove the Authorization header with the Bearer token from your request header and see if it works?
#1
WarrenBelz
146,679
Most Valuable Professional
#2
RandyHayes
76,287
Super User 2024 Season 1
#3
Pstork1
66,015
Most Valuable Professional
