I have questions about the "Server to Server Authentication for Microsoft Dynamics 365 Online" item in the January 2022 Release Notes. Is this method available now (or do we have to wait until Jan 21, as indicated in the release notes)? I see the online documentation was updated to include it as of last week. (Working on an integration now) Is the Sync User set up as a user in Dynamics with a password? Or does it only exist as an Application user? Would MFA still need to be turned off in order to validate the MSD sync, as stated here? Asking since one of the benefits of this method is to be able to use SSO and MFA. When entering Credentials in Marketo to validate or sync, is the password field present and required? It is not shown in the screencap, but confusingly, it is mentioned in the text as required (related to Q2 above). I can certainly direct these questions at Support, but thought I would try for clarification for all, if helpful. Thank you!

Level 3

Solved

Dynamics integration - Server to Server connection

Forum|Forum|4 years ago
January 10, 2022
2 replies
4295 views

I have questions about the "Server to Server Authentication for Microsoft Dynamics 365 Online" item in the January 2022 Release Notes.

Is this method available now (or do we have to wait until Jan 21, as indicated in the release notes)? I see the online documentation was updated to include it as of last week. (Working on an integration now)
Is the Sync User set up as a user in Dynamics with a password? Or does it only exist as an Application user?
Would MFA still need to be turned off in order to validate the MSD sync, as stated here? Asking since one of the benefits of this method is to be able to use SSO and MFA.
When entering Credentials in Marketo to validate or sync, is the password field present and required? It is not shown in the screencap, but confusingly, it is mentioned in the text as required (related to Q2 above).

I can certainly direct these questions at Support, but thought I would try for clarification for all, if helpful. Thank you!

Marketo

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

Best answer by Katja_Keesom

Hi @shannon_kelly1 ,

What I know of the new S2S connection is that it would not use a sync user anymore, so there would also not be a username and password, only client id and client secret. That means that MFA has no impact anymore, as that is related to the sync user.

I know the method has been tested in beta recently, but expect it to only become available for all instances on Jan 21st.

Kind regards,

Katja

Katja_Keesom

Accepted solution

Community Advisor and Adobe Champion

Hi @shannon_kelly1 ,

What I know of the new S2S connection is that it would not use a sync user anymore, so there would also not be a username and password, only client id and client secret. That means that MFA has no impact anymore, as that is related to the sync user.

I know the method has been tested in beta recently, but expect it to only become available for all instances on Jan 21st.

Kind regards,

Katja

S

Shannon_Kelly1Author

Level 3

Thank you, @katja_keesom !
How would we verify what the "sync user" has access to/can view? Typically we would advise the CRM Admin to log in to Dynamics as the Sync User. As there is no Sync User login, would we use a different login and assign it the Sync User Role? That would not be the same 1:1 test...

Katja_Keesom

Community Advisor and Adobe Champion

I haven't seen the S2S solution in action yet, so cannot tell you at this stage. Also not sure who were in the beta, so can't refer you either I'm afraid. We'll have to see when it goes live.

A

akshayk-2

Level 1

1. It is available now, to be declared GA on Jan 21

2. Sync User exists. It is an App user, not Licensed User. That is the only difference The access is based on App user to which you give access.
3. MFA is an advantage, but there is no User ID / password involved . Microsoft promotes App based call higher than the ROPC connection.