Sage 100

Have any brave souls downloaded and used the Office 365 Connector? It appears to be a separate download. I can't tell if there are any instructions that will tumble out when the install is run. There is no separate PDF on the download site. https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=90203&sliceId=1&cmd=&bbid=MSRecommendation916&isDocLink=true&type=Document&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl

I've been wondering about that, too! I have my download and there it sits.

If we wait a month Sage might post something in the middle of the night to Sage City which one of us will spot within another 3 to 5 months..

I downloaded everything, installed and went as far as I could without hooking it into our 365 account. I don't have a play 365 account to mess with!

We are shooting to have this up and running by mid May. Documentation is sketchy right now. Sage is still working on the back end connections for selling the licenses. They need to do a much better job with O365 licenses than they do with Sage 100cloud subscription licenses!

@alanniergarth Am I missing a big sales opportunity for O365 licenses here? Are there that many existing Sage 100 users who don't already have O365 and/or have an IT provider who is managing their network? In my view, once we touch this O365 sales process in the customer's mind we own the installation, configuration, troubleshooting and upkeep for O365. I struggle to see the profit potential here for all but a tiny handful of consultants who also have IT practices. The situation is similar if an IT provider for one of our customers decided suddenly to become a Sage 100 support providers. Sure, you can do it but you probably won't make much money without having prior experience. (Source: Have seen IT providers try to become Sage providers and regret is pretty quickly)

@WayneSchulz It is the integration from Sage to O365 we are interested in. Not licenses per say. We are in the position to offer wrap around services for expanded use of the Office products. Very few IT companies do more than just provide the licenses for O365. Encouraging and promoting adoption is a potential profit center that doesn't step on the toes of most IT partners. We hope to work with them not against them.

@alanniergarth please tell us more. What kind of wrap around services do you see out there with this integration?

In my test env., it installed Azure AD Application Proxy Connector & Updater, IIS Server, .NET 4.6.2 .NET Core, PowerShell. And it required a reboot. It needs an internal URL and defaults to http://localhost/sage100/

I downloaded the connector and couldnt get it setup. I realized that part of the instructions said that you have to ""call sage to get an activation"" - and at that point in the process I sort of just rolled my eyes and set it aside. I dread having to call Sage for anything. Plus as Rhonda said - not only do you need an O365 account to play with that account also needs to be an administrator account. So, I plan on researching more - maybe end of next week.

I'm trying to pin down the Microsoft guy here at Sage Sessions to figure out if we can connect to a Contoso-like account for testing.

@WayneSchulz - The O365 license opportunity will get bigger as 2019 will be subscription only. So in our hosting world we are upgrading our entire AD structure and adding tools to make O365 and Azure federation much more manageable. We just put it in our new SAP cloud and are retrofitting for Sage once fully baked (since we then have to upgrade hosts to Win 2016 Server as well). Sage is actually pretty smart in getting ahead of this (if they can actually get it to work easy).

@WayneSchulz makes a good point about touching then owning O365. I do a fair bit of report development with O365 and its stability has gone down in the last few years. Google ""Microsoft Office unstable?

We have been struggling with the message Sage has been sending about ""ownership"" of the account and who is the CSP. Although Sage wants to be the CSP, it now appears that Sage is requesting and needs administrative privileges when the CSP is not being changed. Microsoft has a provision to have more than one delegated administrator on an O365 account without the account itself being changed.