Working towards a shared outcome/purpose Working together on shared deliverables Need to get all the tools we need to be successful Working together as a team Team appears as virtual identity (e.g., Working on shared queue of incoming requests Answering as the virtual identity, not the individual Working on behalf of a virtual entity History of public conversations Accessible to everyone Discoverable/searchable for everyone Not in the inbox Public, unobtrusive conversations Delivering information into the inboxes of a group of people Direct communications with a group Site Mailboxes Shared Mailboxes Public FoldersDistribution Lists

Site Mailbox Membership Shared Storage Management Owners Members Exchange Site MailboxSharePoint Site IW Views Provisioning Lifecycle Outlook SharePoint

Provisioning Out of the box – from SharePoint site Customized self-service provisioning from Outlook Creating SMs with provisioning systems Deletion Site mailbox is deleted together with SharePoint site Site deletion can be manual or policy driven Site mailboxes are only marked for deletion in Exchange

Lifecycle of a Site Mailbox is controlled through SharePoint policy The scope of the policy is the SharePoint site and Site Mailbox (=project), not the individual item ( , doc) The closed state represents in-place archiving for the project Creation Dramatically simple, shared space creation Integrated with SharePoint Sites Hub Active Use Team is working on project Actively contributing content Accessible through Outlook and SharePoint Closure Project is closed Content is kept for referencing (“archive” state) Accessible through SharePoint only Deletion Content is being deleted from Exchange and SharePoint stores

Enabling site mailboxes in SharePoint and Exchange

SharePoint 2013 pre-reqs  User profile synchronization configured for farm  SSL-enabled web application Exchange 2013 pre-reqs  AutoDiscover setup  Proper RBAC roles to access and manage site mailboxes Mapping  A SharePoint farm points to exactly one Exchange forest where site mailboxes will be provisioned  Multiple SharePoint farms can point to the same Exchange forest  The SharePoint farm must point to a server that is on Exchange 2013

SharePoint  Install Exchange Web Services API to Global Assembly Cache (GAC)  Establish Oauth trust with Exchange  Grant permissions to Exchange server app principal  Enable Site Mailbox feature on SharePoint farm  Set Exchange target domain (either AutoD for arbitration MBX or a specific MBX – needs to be on Exchange 2013 server) Exchange  Create partner app for SharePoint  Establish Oauth trust with SharePoint  Grant permissions to SharePoint server app principal

Diagnostics and troubleshooting

NDR on failed upload (sent for failed upload only to prevent data loss) Using Outlook folder view to see sync issues between Exchange and SharePoint Viewing “site mailbox properties” from their Outlook client

Provisioning UI or Cmdlet (Doc+ Membership)  Triggers initial doc and membership sync  Will retry for 1 min  Successful sync will add Site Mailbox to MBX table  Cmdlet also tries to logon to Site Mailbox directly to get it into MBX table Mailbox assistant (D+M)  Syncs docs and members every six hours  Scoped to active Site Mailboxes who are in the MBX table  Will retry on next sync if failed Sync now button or Update-SM Cmdlet (D+M)  User driven, triggers immediate sync  Update-Sit box project1 BypassOwnerCheck Site Mailbox is open in Outlook/SM app (D+M)  If one or more users has Site Mailbox open in Outlook or the Site Mailbox app, sync will be triggered every 15 minutes Publish doc via Outlook (Document only)  Triggers sync after publish  Also triggered on other OLK actions such as create or delete new folder/message SM App logon denied (Membership only)  Access denied from Site Mailbox app will trigger membership sync  Subsequent retry should work if the user is on the site’s default owners or default members group Maintenance job (D)  Triggers a sync if the site’s URL has been changed