Questions about using a Microsoft 365 shared mailbox as an account

Features
1

Hello

I’m hoping someone will be able to clear this up for me.

Context: I work for a small firm of 3 people and I’m looking to streamline some of our processes using tools like Make, Power Automate and Airtable. Currently all the of us have our own personal microsoft 365 user accounts with mailboxes and there is a generic forwarding list (info@ourbusinessname.com). I am thinking of having our tech support guys convert the forwarding list to a shared mailbox so that we can better manage mail coming into it and send mail from it.

My concern is that even if we convert the ‘info’ forwarding list to a shared mailbox, I will still be unable to create an account on Make/ other platforms and unable to use certain features (Airtable wouldn’t allow me to auto send emails from ‘info’ currently) etc etc. I saw on another thread that 2FA may be an issue too.

Has anyone done something like this before/ can answer my questions or suggest the best way to go about this before I embark on getting tech support involved and getting my boss to sign it off?

Thank you

2

If you want to send emails and save/move/delete etc. in shared mailboxes, yes you need to have a extra user license to put the mailbox under. As a user you can only check your own folders or folder from other users (shared with you). So a shared mailbox is not available because it is not from a specific user. Use this new user to connect to Make and do your thing.

2FA should not be a problem as it is a user interface authentication addon. The API uses OAuth connections. You might need the 2FA when creating the connection in Make, but that would just be once.

1 Like