Summary
Frequently asked questions around the process for adding more than one Microsoft 365 tenant for use with the Sage 200 Professional API, for customer disaster recover, upgrades or in-house testing.
Resolution
Adding a second 365 tenant for testing Sage 200 Professional upgrades and disaster recovery sites follow this article.
Adding a second 365 tenant for testing in-house copies of Sage 200 Professional API for Partners and Developers follow this article.
- How many tenants can you connect?
You can connect as many as required, so long as the 365 tenants are unique and fulfil the Sage 200 licencing you have.
EXAMPLE:
If you are a customer with a live Sage 200 copy, and a Test copy – then we’d expect a maximum of 2 setups for M365.
If you are a customer with a live Sage 200 copy, a Test copy, and a disaster copy off site – then we’d expect a maximum of 3 setups for M365.
If you are a Sage 200 Partner with 15 support staff – then we’d expect a maximum of 15 M365. - How will we tell the API connections apart?
Each connection goes through an onboarding journey with Sage, this involves a unique registration being created. This will be emailed to you – we suggest you keep this safe as well as a record of which Sage 200 serial number this has been paired with. Should you ask us to disconnect one of the licences then you will need to let us know which serial number this is. - Does each Microsoft 365 licence need to have AAD?
Yes, our requirements for this are outlined in this article. - Can we connect the same Microsoft 365 tenant to different copies of Sage 200?
No, this is not a supported scenario. It is expected that both the Microsoft 365 and the Sage 200 Professional that are being connected are unique.