It's compatible.

Thank Jay, but why don't they address Microsoft 365 in the compatibility guide. Do they take it as one and the same thing with Office 2019 ? In a strict environment, one has to provide some evidence why it is not provided. That is why l am looking for formal answers.

Sorry for sounding funny but you know how other clients are.

Microsoft 365 is a continually evolving program with ongoing version updates.  Office 2019 was released in February 2020 as internal version 1808, which is still the internal version number, despite the release of a dozen new builds since the initial release.  At that time, MS365 had the same version number, but it is now up to version 2101. It does not get a perpetual version number like MS Office gets. I presume that Sage simply does not choose to devote the time and expense to test and then update their compatibility document every week or two, which is literally what they would have to do to keep up with MS365 versions.

See https://docs.microsoft.com/en-us/officeupdates/update-history-microsoft365-apps-by-date

Hi Jim, 

Thanks but l don't think its a good enough excuse for Sage.

To some extent they should have at least tested one of the builds or patch for MS 365. So how do they keep up with the industry if they are not prepared to test and provide their clients with adequate solutions. 

Anywhere l guess that's it . They have chosen not to include it in their Compatibility guides.

Thank you .

Hi Jim, 

Thanks but l don't think its a good enough excuse for Sage.

To some extent they should have at least tested one of the builds or patch for MS 365. So how do they keep up with the industry if they are not prepared to test and provide their clients with adequate solutions. 

Anywhere l guess that's it . They have chosen not to include it in their Compatibility guides.

Thank you .

As an example of the type of unexpected changes that MS rolls out to the continuously evolving platform of MS365, approx two weeks ago Microsoft rolled out an update that changed their security protocols so that the create object class no longer opens Excel on MS365. This is a very major change that Sage had no control over and had no way of knowing would occur. This MS change may mean that any customizations opening excel using the create object class will need to be re written. Somebody would have to pay for testing such unexpected changes that can sometimes occur on a weekly basis and the demand for support would also increase. Look more towards your business partners to test, keep up with and support adequate business solution, especially third party solutions.

Hi Angel,

Thanks for your valuable response. 

I suppose Sage 300 is avoiding supporting a product of different pricing model with one of a different price model. Therefore, Sage300Cloud will be fully supported as they are both a SAAS products.