Welcome to Microsoft Q&A Forum!
Have a good day and I hope you're doing well!
I completely understand your concern. To confirm whether this was specific to your environment, I attempted to reproduce this scenario in my test tenant. I configured a Shared Mailbox with the necessary delegate permissions and called the findMeeting endpoint.
I received the same "Unsupported Scenario" result as you did.
Based on my research into the backend architecture, here is the likely reason for this behavior:
The findMeetingTimes API is designed to be "context-aware." It calculates suggestions based on complex user data, such as personal preferences, working hours, and time zones.
- User Mailbox: Possesses an interactive identity and a complete user profile context.
- Shared Mailbox: In the backend (Azure AD/Exchange), a Shared Mailbox is technically a disabled user object without an interactive login session.
When calling this API via delegation targeting a Shared Mailbox, the system likely cannot load the full "user context" required for the calculation algorithm to execute. It appears this specific API capability is restricted to fully licensed, interactive user accounts by design.
Currently, I also could not find any official documentation explicitly listing Shared Mailboxes as an unsupported scenario for this endpoint.
However, the reproduction results suggest that this is the current behavior of the API for Shared Mailboxes, confirming that the issue is not with your implementation or code logic.
As a forum moderator, I am sharing this insight based on my own testing and research to help clarify the behavior. I hope this explanation saves you time from further troubleshooting.
Best regards.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.