[Fixed]: The Mail connector is currently restricted for new tenants

In this blog, we will learn how to fix error: “The Mail connector is currently restricted for new tenants. Microsoft is working on enabling this connector. In the meantime, please consider using alternatives like Office 365 Outlook, Gmail, SendGrid connector instead.”

Issue: The Mail connector is currently restricted for new tenants

Basically, we will get this error “The Mail connector is currently restricted for new tenants” while we add this email connector “Send an email notification (V3)” in our flow.

Why do we get this error in Power Automate?

The error message we encountered in Power Automate regarding the Mail connector being restricted for new tenants indicates that Microsoft has temporarily limited access to this particular connector for newer tenants. As a result, users are advised to consider using alternative connectors like Office 365 Outlook, Gmail, or SendGrid to integrate email-related functionalities into their workflows.

Here are a few reasons why you might encounter this error:

• Connector Restriction for New Tenants: Microsoft sometimes restricts access to specific connectors, especially for newer tenants or during updates, to ensure a smoother experience for users. The restriction may be temporary and related to ongoing improvements or maintenance.
• Service Updates or Improvements: The restriction might be in place due to updates, improvements, or enhancements being made to the Mail connector. Microsoft could be working on enhancing its features or addressing any issues to provide a more robust and reliable experience.
• Promotion of Alternative Connectors: The error message suggests using alternative connectors like Office 365 Outlook, Gmail, or SendGrid as viable options during the restriction. Microsoft is encouraging users to explore and utilize these alternatives for email-related actions within Power Automate.
• Tenant-Specific Configuration: It’s possible that the configuration or restrictions are specific to your tenant, and Microsoft is implementing a tenant-specific policy or setting regarding the usage of the Mail connector.

To work around this issue, consider following the recommendation and utilizing the suggested alternative connectors (Office 365 Outlook, Gmail, SendGrid). These connectors should allow you to achieve similar email-related functionalities within your Power Automate workflows while the Mail connector is temporarily restricted. Additionally, keeping an eye on updates from Microsoft regarding the status of the Mail connector for your tenant is advisable to know when it becomes available again. You can refer to this Microsoft article for more details: Known Issues and Limitations in Send an email notification (V3)

[Quick Fixed]: The Mail connector is currently restricted for new tenants

There are two send email notification connectors in Power Automate: “Send an email notification (V3)” and “Send an email (V2)“. Just replace your “Send an email notification (V3)” action with “Send an email (V2)” and your issue will be fixed. Know the difference between “Send an email notification (V3)” and “Send an email (V2)” from this article: Power Automate Send Email: Difference between “Send an email notification (V3)” and “Send an email (V2)”

Summary: The Mail connector is currently restricted for new tenants

Thus, in this blog, we have learned about how to fix this error. “The Mail connector is currently restricted to new tenants. Microsoft is working on enabling this connector. In the meantime, please consider using alternatives like Office 365 Outlook, Gmail, and the SendGrid connector instead.” when we get by adding the “Send an email notification (V3)” action.

See Also: Power Platform Troubleshooting

You may also like the following Power Platform troubleshooting articles:

• [Fixed]: Unable to Export Flow as a Zip Package
• [Fixed]: Power Automate connection not found. Please create a new connection and change your application to use the new connection.
• Instantly Solved: Error from token exchange: Bad Key authorization token in Power Automate – Microsoft 365
• Get Items Filters Not Returning Values? No Problem! Here’s How to Fix It in 2 steps

About Post Author

MA Microsoft Techy

I am an Enterprise Architect with 20+ years of experience in Microsoft technologies, specializing in Power Platform, Microsoft 365, governance, AI-driven solutions, and enterprise automation. I share my technical expertise with the community through my blog and YouTube channel: https://www.youtube.com/@MicrosoftTechy

See author's posts