\r
## Setup\r
\r
-1. LOL. It defaults to `bash`. Change that.\r
+1. Start a cloud shell on the Exchange Admin website. \r
\r
-2. Probably one-time install\r
+2. The cloud shell defaults to `bash`. Change it to `PowerShell`.\r
+\r
+2. Run these commands once. \r
+\r
+ The results of these commands will persisit in your Cloud Shell attached Azure storage.\r
\r
```powershell\r
Install-Module -Name PSWSMan -AcceptLicense -Confirm\r
Import-Module ExchangeOnlineManagement\r
```\r
\r
-3. Probably per session:\r
+3. Repeat these commands for each new Cloud Shell\r
\r
```powershell\r
Import-Module ExchangeOnlineManagement\r
\r
### Distribution Group\r
\r
-Seems like this is an older way to do it.\r
+A distribution list sends a copy of any incoming email to the inbox of every member. The list itself, has an email address, but does not have a mailbox, since a copy of every incoming message goes in the mailboxes of each list member.\r
\r
1. Create distribution group\r
\r
\r
### Or create an entire shared mailbox\r
\r
+A shared mailbox is an actual separate mailbox. Messages sent to it will not be copied into the mailboxes of the members with access. Members with access to a shared mailbox may also be allowed to send email out.\r
+\r
+A shared mailbox should be used if:\r
+\r
+ - A team of people need to send email out from the email address\r
+ - Each email should only be handled by one person.\r
+\r
+> Warning: This recipe is likely incomplete, as I eventually decided not to use it.\r
+\r
1. Create a shared mailbox\r
\r
```powershell\r