Graph API Presence should support Application permissions

is there a reason that the subscription API does not support presence subscriptions using application level permissions https://learn.microsoft.com/en-us/graph/changenotifications-for-presence since the presences can be fetched using application level permissions?

Does this suggest that applications should poll the presence API for changes?

AnnieWang It would be interesting also to be able so set the presence of an user with app permissions.
At the moment we have implemented a workaround using delegated permissions but this system is not optimal as it requires polling from several web pages.

Hello, is there any new info about presence subscriptions to support app permissions since we are in CY24H3? AnnieWang 

ChrisPreston and MFerris4 presence subscriptions to support app permissions is being considered in CY24H2 but there's no set date on this. 

The documentation says for "Application" the "Least privileged permissions" is "Presence.Read.All", however in the App registration applications permissions Presence section only lists "Presence.ReadWrite.All". 

Thanks AnnieWang and the team for getting this out in beta and thanks for keeping us all in the loop in the meantime!

Do you have any estimate on subscription availability?

It would be really helpful for managing customer expectations! 

This is working as expected so far via the communications/getPresencesByUserId call - so thanks to the team for working to get this out in Beta!

AnnieWang Do we know when/if this will become available via a subscription? I did try to see if this was enabled already, but that doesn't seem to be the case unless I'm missing something?

Thanks!

The documentation still claims this is not supported

https://learn.microsoft.com/en-us/graph/api/presence-get?view=graph-rest-1.0&tabs=http#permissions

Am I missing something?

Thanks everyone for being patient about this feature. 

And DarrelMiller couldn't have done it without you, so thank you as well! 

Corey Richardson and everyone else on this thread.  Thank you all for your feedback.  You may sometimes think that these comments fall on deaf ears but they do not.  It took us too long to get here, but your feedback was a major influence on helping to prioritize this work over other features.

And thank you to AnnieWang for stepping up and representing your team here when this feature request was already old enough to walk.  I know how hard it is to be the messenger between a frustrated community and product team that have a wide range of pressures driving the backlog of work.