# A0deploy import error saying "There is not a configured email provider"

**URL:** <https://community.auth0.com/t/a0deploy-import-error-saying-there-is-not-a-configured-email-provider/169603>\
**Category:** Get Help\
**Tags:** other, missing-category\
**Created:** [January 21, 2025, 4:42pm UTC](https://community.auth0.com/t/a0deploy-import-error-saying-there-is-not-a-configured-email-provider/169603 "2025-01-21T16:42:47Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![danclarke-smve](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/danclarke-smve/32/57893_2.png) [@danclarke-smve](https://community.auth0.com/u/danclarke-smve)\
**Post date:** [January 21, 2025, 4:42pm UTC](https://community.auth0.com/t/a0deploy-import-error-saying-there-is-not-a-configured-email-provider/169603/1 "2025-01-21T16:42:47Z")

</div>

I’ve exported using a0deploy export, then tried reimporting the same config. I haven’t modified the exported config at all. It fails on import with this error:

```auto
2025-01-21T16:30:21.676Z - error: Problem running command import during stage processChanges when processing type emailProvider
2025-01-21T16:30:21.676Z - error: There is not a configured email provider

```

There’s a bunch of success entries above - so it’s working for a lot of the config files, just failing at this point.

In the `tenant.yaml`, email provider is this:

```auto
emailProvider: {}

```

And in the portal, “Use my own email provider” is unchecked.

Given I haven’t touched the exported config files - is this a bug?

Thanks,  
Dan

---

<div class="post-metadata">

**Author:** ![rueben.tiow](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/rueben.tiow/32/11646_2.png) [@rueben.tiow](https://community.auth0.com/u/rueben.tiow)\
**Post date:** [January 21, 2025, 7:56pm UTC](https://community.auth0.com/t/a0deploy-import-error-saying-there-is-not-a-configured-email-provider/169603/3 "2025-01-21T19:56:04Z")

</div>

Hi @danclarke-smve,

It seems that the error is being thrown because of the email provider configuration object being imported. It is missing the required properties to define the `emailProvider` object, like the name and credentials. For example:

```auto
emailProvider:
  name: sendgrid
  credentials:
    api_key: '##SENDGRID_API_KEY##'
  default_from_address: example+support@sample.com
  enabled: true

```

If you do not use an email provider configured, could you try removing the entire line `emailProvider: {}` from your tenant.yaml file and reimport again?

Thanks,  
Rueben

---

<div class="post-metadata">

**Author:** ![danclarke-smve](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/danclarke-smve/32/57893_2.png) [@danclarke-smve](https://community.auth0.com/u/danclarke-smve)\
**Post date:** [January 22, 2025, 9:13am UTC](https://community.auth0.com/t/a0deploy-import-error-saying-there-is-not-a-configured-email-provider/169603/4 "2025-01-22T09:13:36Z")

</div>

Thanks @rueben.tiow. But given the export is including that `emailProvider` entry - surely this is a bug? It feels like I should be able to export and then reimport without having to write text-parsing code to remove a particular entry before importing.

---

<div class="post-metadata">

**Author:** ![rueben.tiow](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/rueben.tiow/32/11646_2.png) [@rueben.tiow](https://community.auth0.com/u/rueben.tiow)\
**Post date:** [January 27, 2025, 11:49pm UTC](https://community.auth0.com/t/a0deploy-import-error-saying-there-is-not-a-configured-email-provider/169603/5 "2025-01-27T23:49:24Z")

</div>

Hi @danclarke-smve,

You’re absolutely right that you should be able to export and re-import without having to make any changes to the file.

However, judging from the error message, it seems like the `emailProvider` object was malformed.

As a workaround to not using the `emailProvider`, you can exclude it from being managed:

```auto
{
  "AUTH0_EXCLUDED": ["emailProvider"]
}

```

Thanks,  
Rueben

---

<div class="post-metadata">

**Author:** ![danclarke-smve](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/danclarke-smve/32/57893_2.png) [@danclarke-smve](https://community.auth0.com/u/danclarke-smve)\
**Post date:** [January 28, 2025, 4:00pm UTC](https://community.auth0.com/t/a0deploy-import-error-saying-there-is-not-a-configured-email-provider/169603/6 "2025-01-28T16:00:51Z")

</div>

Great! That works perfectly - thank you 🙂  
I just need to remember to remove it if I ever add a custom email provider! 😂

---

<div class="post-metadata">

**Author:** ![rueben.tiow](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/rueben.tiow/32/11646_2.png) [@rueben.tiow](https://community.auth0.com/u/rueben.tiow)\
**Post date:** [January 29, 2025, 12:25am UTC](https://community.auth0.com/t/a0deploy-import-error-saying-there-is-not-a-configured-email-provider/169603/7 "2025-01-29T00:25:05Z")

</div>

Hi @danclarke-smve,

I’m glad it worked!

Aha yes, please remember to remove it when you add a custom email provider. 😅

Let us know if there’s anything else we can do to help!

Best regards,  
Rueben

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [February 12, 2025, 12:25am UTC](https://community.auth0.com/t/a0deploy-import-error-saying-there-is-not-a-configured-email-provider/169603/8 "2025-02-12T00:25:29Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
