Hi

Did you get a reply on this? I've got the same exact problem.

Thanks 

Bea 

Hi

Did you get a reply on this? I've got the same exact problem.

Thanks 

Bea 

I haven't seen any updates or replies on this, so I'd just ask if you've applied the 2022 R2.1 patch, and if so, did that fix the problem for you?

Hi

No, I was told I had to allow each individual to log onto the server directly (2500+), which clearly is not an option for us. We only allow desktop access so I was offered no solution. 

We then decided we would change from HTTP to HTTPS, with the pain this would cause. I am testing this approach which seems to work product wise, not for us as a company. 

We will hopefully be dropping Sage CRM within the next few years and will be moving to a product that actually cater for our company's need.

Hi Bea

The experience for a user connecting to their account should be pretty pain free.  Once the administrator has set up the new 'app' then each user can authorise access just by filling in their details in the pop up - like logging on to web mail etc and they should be good to go.

Hello

Thank you for your reply.

I am the administrator but at no point was it suggested to me that there would be an app. to make this accessible to the users.

Hi Bea

The documentation for the set up is here:  Steps to enable import of contacts and email messages (sagecrm.com)

As part of the steps to obtain OAuth 2.0 client ID and secret value that you will use to configure Sage CRM you
will need to access the Azure Active Directory admin centre as an administrator and register a new 'App'. - That's the Microsoft terminology.

I created a video about the new feature and its configuration here:  https://youtu.be/IsvwWMFsFCE?t=541

Hi 

We have d one all of that. Unfortunately when the users try to log into Sage CRM from their desktops the error message originally reported here appears. It's only whilst logged onto the server the users can change their preferences. I actually logged an incident with yourselves only to be told we had to allow users to log into Sage CRM directly on the server, which we cannot do. Hence trying the HTTPS route which does allow users to change those from their desktops. 

Bea 

Hi Bea,

That is what I was told by support as well and it is not really a workable solution to get each user to log onto the server, particularly with your user numbers! I created a SSL certificate on my local domain and assigned that to the site and was then able to connect using https with the FQDN of the CRM site. This meant the web browser saw it as a secure site and the user was then able to link their Mailbox successfully.

The "App" link you create in Azure has an expiry and my initial one was set to the default of 6 months and expired shortly after going live. It took me a while to figure out what had happened. I then had to create a new secure secret and update this in CRM. This seemed to require the users to then reauthenticate with Office 365 in CRM before they could access their Mailbox again - a real pain having just set it up. The maximum setting for a client secret is 2 years so I set it to that.

Having done all this our staff who previously used the Outlook CRM Plugin all said the new method was far too slow and clunky! We tried to install the CRM Plugin that came with 2022 R2 but it crashed when loading in Outlook and did not work. We eventually found a version from 2022 R1 that worked and most of our staff are using that rather than the new method!

Mark.

What a  fantastic, comprehensive reply. THANK YOU. 

I will take all of this onboard and will discuss with the users. This is so unsatisfactory.

Thanks again

Bea 

Ah!  OK - do you know if the issue you have logged has been escalated to the L3 team in Dublin? 

Yes, the issue was escalated to Dublin but Newcastle got back to me with the suggestions we followed. I'm thinking we won't be using the new feature, although I might follow the advice from Mark: 'We eventually found a version from 2022 R1 that worked and most of our staff are using that rather than the new method' and see how it goes.