I’m automating a legal knowledge-base agent in Amazon Quick. A scheduled task reads emails sent to our team alias and files them as Markdown documents in a SharePoint library, with no manual approval. It works well in testing.
The production alias, however, is a Microsoft 365 group (…@groups.amazon.com). Its emails land in the group mailbox, not in members’ personal inboxes. From what I can see, the Outlook connector only reads the signed-in user’s own mailbox:
the group mailbox doesn’t appear in the folder list;
none of the available mail tools let me target another mailbox address.
My questions:
Is there a supported way for a scheduled agent to read a group mailbox directly?
If not, is this on the roadmap?
Is the recommended workaround to turn on “Follow in inbox” on the account running the task, so group emails are copied to its personal inbox?
My concern with that workaround is that it ties the whole process to one person’s account and inbox.
I believe that you’re right that the connector can’t get at the group mailbox. Its mail actions work on mailboxes and their folders, and neither of its permission tables includes a Group or Group-Conversation permission (Outlook integration). That matters because Graph’s mail API covers primary and shared mailboxes (overview), while Microsoft 365 group mail comes through the group conversations API, which needs at least Group-Conversation.Read.All (List conversations). So there’s no documented way to read the group mailbox directly, and I couldn’t find anything public about it being on the roadmap.
“Follow in inbox” works the way you describe: group mail lands in the follower’s inbox and is still kept in the group folder (Microsoft Support). To avoid tying it to one person, one idea I have is to have your Exchange admin create a dedicated mailbox, add a mail flow rule that Bccs it on messages with the group address in To or Cc (conditions, actions), and connect Outlook in Quick as that account. With the default or custom OAuth app, the connector acts as whoever signs in to Microsoft, and I couldn’t find Quick docs on signing in with an account other than your own, so test that part first. Two gaps to know about: the rule won’t catch mail where the group was only Bcc’d, and it only matches the group’s primary address, not any secondary addresses.