#Outlook/Teams/Gmail41 discussing

This is a very common gotcha — the default login screen in the Outlook integration shows username/password, but SSO is there, it's just hidden behind the Custom Domain step. Here's exactly what your users need to do:

1. Open Outlook and click the Salesforce icon in the sidebar or ribbon to open the Salesforce panel
2. On the login screen, look at the bottom and click "Use Custom Domain"
3. In the field that appears, type your org's My Domain name — just the subdomain, not the full URL (e.g. if your login URL is yourcompany.my.salesforce.com, enter yourcompany)
4. Click Continue
5. The screen will now show your SSO login button (usually labeled with your company name or identity provider, e.g. "Log in with Microsoft" or "Log in with Okta")
6. Click that button and authenticate through your normal SSO flow

Once they've done this once, Outlook should remember the custom domain for future logins.

If the SSO button still doesn't appear after entering the custom domain, check two things in Salesforce Setup:

• My Domain → confirm "Deploy to Users" has been clicked (not just enabled)
• My Domain → Authentication Configuration → make sure your SSO provider is checked under "Authentication Services" — if it's unchecked, users won't see the SSO option even with the right domain entered

Hope that gets them sorted!

Hi Tony, 

Great question! Here's what you need to know about using alternate email addresses with the Salesforce App for MS Teams: 

Short answer: The Salesforce App for MS Teams uses the email address tied to your Microsoft/Teams identity (i.e., your Outlook/M365 login) when creating meeting invites and Teams chats — it does not natively allow you to swap in a different "from" email address like your SF business email. 

However, here are your options: 

1. Map the correct email in Salesforce User settings: 

Make sure each Salesforce user's Email field matches their Outlook/M365 email (

). The Teams app uses this mapping to link identities. If the emails don't match, it can cause issues with record association and invite creation. 

2. Use Microsoft 365 email aliases: 

If your org uses M365, you can add

as an email alias on the user's M365 account. This way, both email formats are associated with the same mailbox, and Teams meeting invites will still work correctly regardless of which format is used. 

3. Salesforce Inbox / Einstein Activity Capture: 

If you're using Salesforce Inbox or Einstein Activity Capture alongside the Teams integration, you can configure which email address is used for activity logging. This won't change the Teams meeting invite sender, but it helps ensure activities are captured against the right Salesforce records. 

4. Custom workaround via Flow + Teams Connector: 

For full control over meeting invites with a specific email, some teams use a Salesforce Flow + Microsoft Power Automate (Teams connector) approach to generate Teams meeting links programmatically and send them from the desired email address. 

My recommendation: Start with Option 2 (M365 alias) as it's the simplest and doesn't require any Salesforce config changes. Hope this helps!

@Siddhesh Paratane

I just went through this process and using your example, you'll want to put this in the Name field: key1._domainkey 

And this in the Data field:

I created a separate custom record in Squarespace for the Alternate CNAME Record in Salesforce.  

As soon as I entered that data, the 'activate' button became clickable in Salesforce. 

Hi @Andrej Kolaja

This is expected behavior in many Salesforce setups. Events sent directly from Salesforce are often delivered as informational emails rather than full calendar meeting requests, so external recipients may not see the Accept/Decline options. 

Since your requirement is for customers to respond to invitations and for those responses to be tracked, the recommended solution is to use Outlook Integration/Salesforce Inbox and send meetings through Outlook. This sends a proper calendar invitation that recipients can accept, decline, or mark as tentative, and their responses can be synchronized back to Salesforce. 

Recommend reviewing your Exchange configuration to confirm that calendar invitations are being processed correctly.

It is a little confusing, but I had Claude draw a picture -->

Your Outlook Integration is good, but the Lightning Sync will need to migrate to Einstein Activity Capture 

@Marie Chough

the first thing you need the Global Actions for create New Contacts.  Then if you are using Outlook Integration And Lightning Sync -> specific 'Email Application Publisher Layouts' -> you need to add/remove the Global Action into the specific layout on Quick Actions OR If the profile in use is not assigned in a Email Application Publisher, so you need to add/remove it on Setup -> Publisher Layout Quick actions, for the Publisher Layout assigned to the profile. 

Some links: