Exchange Online Migrate doesn't work seem to convert to MSGraph

Hello Timkn,

This appears to be an issue. It is not working for me either, and we are currently checking it with the Lab team.

I will update you once we have a solution.

Thanks,
Arvind

Worked with support and got this to work.  I thought I would document the steps here as it appears it is not limited to our environment according to support.  The big problem is that the Migrate button only performs some of the steps required and doesn’t switch you from using EWS to MSGraph which come October I imagine is going to be a nasty suprise for some people.  The gotcha is that mail and task notifications will work after running through the Exchange Online feature successfully and you’ll think great I’m done and forget about it until October when EWS is deprecated and your workflows break.

So the steps for me, granted may be a bit different than on-premise, since the K2 Server is member servers and not connected to a domain so they’re initially configured as K2SQL and then integrated with Azure Active Directory (Entra).

1. Change the runtime to allow for Msforms authentication
2. Login using K2admin k2sql account
3. Delete the saved token from Resource Tokens (this was vital but not documented as it appears its this token which calls MSGraph and before this I was getting an access denied).
4. Run the Migrate/Update for Exchange Online
5. Logout when asked by clicking the link
6. Continue in the Migrate/Update wizard
7. Login to K2 Management using the mail account (which in our case is different than the service account and with EWS had no K2 persmissions so will first need to give it Admin permissions (or at least I did).
8. In the below article follow Step 4 - Edit the connection strings and first delete the existing EWS connections and then add the MSGraph ones.
9. Modify the K2HostServer.exe.config file to comment out the EWS and add the MSGraph tag described in that article in Step 5: Still within the K2HostServer.exe.config file and if you are using SmartActions, check if these properties: enableListeners="true" and "SmartActions\MSGraph" are set. If "SmartActions\EWS" is listed under directoryCatalog, please comment it out, as in the image below.

https://help.nintex.com/en-US/nintexautomation/icg/5.8.1/Content/Configure/ExchangeOnline/ExchangeOnlineManual.htm

That finally worked.  I haven’t tried it on another server yet but will soon.

Thats great.. still this is not working for us and this is with support since some time. 

This does appear to be a right mess. I’ve been messing with updating to Graph for the past few weeks. 

There is no mention of running migrate in the guidance 4.8.1. We assumed you left the original EWS Exchange Online feature as is and manually created a new one for Graph. I now have a ticket with Nintex which hasn’t had a response for a while… Why can’t they provide a complete guide that actually works, including complete switchover and removal of EWS Exchange so that we know 100% Graph is working now and no nasty surprises in October. Don’t know about you guys, but Nintex support isn’t what it used to be...

Hi Sharpap1 and Arvindsct.  I’m curious if you ever got your environments working?

We’re just about to start the process of rolling this out to customer servers and wondering about other people’s experience.

Regards,

Tim

Hello Tim,

Yes its working for us.  we did some fix. 

Please contact me , I will help you on this

Automate@proinception.com

Thanks,
Arvind Kumar

Hi Arvindsct

I do have it working in our test enviroment.  However, I was surprised that after restarting the test server thats been dormant for months the email stopped working.  Logging in to K2 Management using the mailbox account resolved the issue (or at least thats my working theory).  I’m wondering if other people have experienced that?

Regards,

Tim

Hello Tim,

Check the Graph API permission and logs.

Hi,

We did get Graph configured with the help of support, however going to Graph has caused major problems with all our Legacy Workflows.

We discovered while testing Graph afterwards, that using K2 with Graph and legacy Workflows breaks down when using special HTML containing double-quotes in the body of Email events. Any K2 Studio process will error that contains HTML. The HTML worked fine in EWS, but not Graph.

Currently, we passed these findings to K2 and have been waiting quite a while now for a fix. If there is no fix, we will have to edit each and every event mail activity in every workflow. This has really impacted our organisations upgrade plans as well as the amount of time I’ve personally had to spend troubleshooting these upgrade/graph issues.