IT Configuration



Be sure everything around IT works smoothly for Workplace.
Overview

Overview

Workplace will send emails to users of your instance, such as:

  • Invitations for members of your organization to claim their accounts.
  • Notifications when an organization member is mentioned in a post or comment.

Email notifications are a driver for Workplace engagement. It is essential that emails sent by Workplace are not blocked by your organization's email infrastructure.

?
If you're not receiving emails from Workplace, check that you haven't changed your email notifications settings. If the issue persists, you should contact your IT department. They will likely be able to perform a check of the controls described in this guide.

This guide provides information on the mail servers used to send emails so that you can ensure these emails are deliverable.

Ensuring Email Delivery

Email domains

Email domains

Every single email that is sent by Workplace will originate from the domain fbworkmail.com.

Your email administrator must add fbworkmail.com as a safe sender to your email host, otherwise people in your organization will not be able to receive claim account emails and will not be able to join your Workplace instance.

Email servers

Email servers

Your email administrator must whitelist these email origin servers' IP addresses to ensure that your organization does not reject Workplace emails.

66.220.144.128/25​(66.220.144.128​-66.220.144.254​)​
66.220.155.128​/25​(66.220.155.128​-66.220.155.254​)​
69.171.232.128​/25​(69.171.232.128​-69.171.232.254​)​
69.63.178.128​/25​(69.63.178.128​-69.63.178.254​)​
69.63.184.0​/25​(69.63.184.0​-69.63.184.126​)
Verify email origin and DKIM

Verify email origin and DKIM

To prove that emails coming from fbworkmail.com actually originate from Facebook, Workplace uses the industry standard technology DomainKeys Identified Mail (DKIM).

Your email administrator should configure your mail host to verify the DKIM record of all Workplace emails to ensure that you do not accept spoofed emails.

Check email client spam filters

Check email client spam filters

Even if your mail host accepts emails from Workplace, it is still possible that email clients like Microsoft Outlook will mark an email as Spam or Junk. In this case, a person would have to check their Spam or Junk folder to find the email. If possible, your email administrator should centrally push a rule to all email clients adding fbworkmail.com as a safe sender.

Work with your email administrator to add the fbworkmail.com domain to the Safe Senders list in your organization's email client for all of your people.

Configure Microsoft Outlook

Configuring Microsoft Outlook Clutter and Focused Inbox

To keep Workplace emails from being lost in Microsoft Outlook Clutter, use the PowerShell Exchange Online Commandlet to create two transport rules:

> New-TransportRule -Name "Workplace Emails Bypass Focused Inbox" -SenderDomainIs "fbworkmail.com" -SetHeaderName "X-MS-Exchange-Organization-BypassFocusedInbox" -SetHeaderValue "true" -Comments "Workplace email will go into the Inbox or Focused Inbox and not the Clutter or Other folder in Exchange Online"

> New-TransportRule -Name "Workplace Emails Bypass Clutter" -SenderDomainIs "fbworkmail.com" -SetHeaderName "X-MS-Exchange-Organization-BypassClutter" -SetHeaderValue "true" -Comments "Workplace mail will go into the Inbox or Focused Inbox and not the Other view in Exchange Online"
Configure Microsoft Exchange

Configuring Microsoft Exchange

With Microsoft Exchange, you can whitelist the Workplace email domain using the Set-MailboxJunkEmailConfiguration cmdlet.