web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Answered

How do I make sure my Sandbox environment copied from Production does not inadvertently send out emails to customers and vendors?

(0) ShareShare
ReportReport
Posted on by 39

We had a previous issue where our Sandbox environment (copied from production) sent email invoices out to customers.  We were advised there are 2 ways:  1. Disable SMTP and/or all job queues in relation to sending out invoices or statements from the environment; 2. Use config packages to change all email addresses to internal email addresses for vendors and customer.

How to I do No. 1?

I have the same question (0)
  • Suggested answer
    MahGah Profile Picture
    15,529 on at

    Hi

    In BC SaaS when you create Sandbox by default it put all Job Queue on hold. But you can search for Job Queue then put them all on hold. 

    But to disable SMTP if you are on newer version of BC (20 and up) go to Email Accounts then delete all emails. This way BC has no email setup to send email out. 

    The second method is overkill and complex. As far as you do not have SMTP or email setup in place you should be good to go. 

  • lisapedrosa Profile Picture
    39 on at

    Hi MahGah,

    Thank you very much for your quick response.  Allowed me to proceed with more confidence as it would be a nightmare if the Job Queue sent out emails by mistake like it did before.

    Could it be that a recent update has now disabled Email Accounts on newly created Sandbox environments?  It appears that there were no emails in "email accounts" in the copied environment as well.

    pastedimage1656373827258v1.png

  • Suggested answer
    MahGah Profile Picture
    15,529 on at

    You are welcome.

    That is a news to me since I created Sandbox 2 days ago and has Email Accounts still active.

    usually what I do right after creating Sandbox is

    1) Make sure all Job Queue are on hold.

    2) Delete all emails from Email Account (if disabling that service prevent emails is even better, I will test next time).

    3) Go to SO (or somewhere else) to test and see if I can send email.

    4) We have one email (such as test@domain.com) for this email we have a rule that stop this email to send email outside of our org (in exchange email setup).

    5) I set that email as a default email for everything in Sandbox (SMTP setup). This way I still can test and if by mistake anything run it will be through that email that cannot go outside of org.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 3,010

#2
Jainam M. Kothari Profile Picture

Jainam M. Kothari 1,270 Super User 2025 Season 2

#3
YUN ZHU Profile Picture

YUN ZHU 1,085 Super User 2025 Season 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans