As I said in my post, as it is O365 and I am using Application ID with Secret for the connection in O365 Scope. The Account ID has to be the “User Account”, as per the documentation. Without that, no emails are available.
But just trying to understand if that Client ID and secret has the access to the shared mailbox. If yes I believe we can use it in the account field of the activity.
Hi NK,
Not sure if there is some confusion here.
The “Application ID” and “Secret” give access to O365.
The “Account” is the user for the context.
The Shared mailbox is not a “User”.
When accessing Outlook with the “User” account, they can access the Shared Mailbox.
FWIW, we also use O365 activities with Application ID and Secret authentication, and for our Outlook activities we provide the shared mailbox email address in the ‘Account’ property to access the shared mailboxes.
Thanks for sharing your experience.
We have tried that and it did not work.
It complained that the “Shared Mailbox” did not have access. In my opinion, that is correct. The Shared mailbox does not have any user permissions associated with it.
Are your Shared mailboxes created as full users in Outlook 365?
I believe we also had that error, and would always get it for new shared mailboxes, until infrastructure would add the shared mailbox address to the Azure app. I always thought it odd, but it worked.
I don’t think the shared mailboxes are full users and my understanding is they don’t consume an O365 licence. I could be mistaken on that though. I’ll have to go digging for more info, it’s been quite some time since it was all set up.