Cannot create a new Business Central cloud Sandbox environment from Production

Hi experts,

In Business Central Administration Center, I try to create a new Sandbox environment. I want it to be a copy of Production. When I do so, it is shown in the list of environments (with status "Preparing" if I remember it right). After 5-10 minutes, the environment is gone again. No warnings. No error messages.

My customer is allowed to have 3 Sandbox environments and they only have one other.

I have had this problem for 3-4 days now. I could do it with no problems for 2-3 weeks ago.

Today I can also create new Sandbox environments - but not if they are a copy of Production.

I hope, you can help.

Best Answer

  • JuhlJuhl Member Posts: 720
    Accepted Answer
    Its a bug. They are working on it.
    Workaround is to delete all sent mails from outbox/sent mails.
    Follow me on my blog juhl.blog

Answers

  • JuhlJuhl Member Posts: 720
    Accepted Answer
    Its a bug. They are working on it.
    Workaround is to delete all sent mails from outbox/sent mails.
    Follow me on my blog juhl.blog
  • MortenSteengaardMortenSteengaard Member Posts: 84
    Hi Juhl,

    Thank you for your reply. You are really my hero today!

    Microsoft couldn't tell us what to do, but you could!

    We deleted the e-mails and now our problem is solved and everything works fine.

    I have written to the one at Microsoft, that should handle my case, that you told me the solution.

    Now we are able to test our extension on data from Production and deliver as planned.

    Once again, thank you!
  • JuhlJuhl Member Posts: 720
    I talk to them yesterday and they confirmed the bug, so thats wierd.
    Follow me on my blog juhl.blog
  • AdalbertAdalbert Member Posts: 9
    For two BC install's we faced the same issue although we didn't have any mails yet.
    The following weird solution helped:
    - signin azure portal
    - click AAD -> Users
    - select user
    - assign roles
    - add Dynamics 365 Admin role (???)
  • MortenSteengaardMortenSteengaard Member Posts: 84
    Microsoft has informed me that the error is corrected. I have tested it, and it works now.
Sign In or Register to comment.