Hello Luciano,

The 404 can come from any on of the service calls.

Did you configure all the site properties needed ? 

What do the platform logs tell you ? 

Best Regards,

Miguel Amado

Hi Miguel,

    after solving the problems of configuration there is no error in the log. The configuration and access to Microsoft is configured and it seems it worked well. The problem is after authentication.  I added the MicrosoftLoginConnector/Callback.aspx and checked that the callback is there, but for some reason OS says that there is not this url... weird.

Follow the log.  Any idea ?

Best regards

Luciano Schiavo

After debugging I realized that the problem could be the size of parameters delivered by Azure.  When I cut part of the code parameter the page hits the callback and follow the flow.  Someone knows how to solve this ?  Below an adjusted url to give an idea of the size of parameter transferred.

https://myenvironment.com/MicrosoftLoginConnector/Callback.aspx?code=AQABAAIAAAAP0wLlqdLVToOpA4kwzSnx3XiKx098hTtEyGlaVEgG7wAQbWJ1IlXaTbsOhkllNMNKaFZczauLfPgiHHFZyer7GQawBh0-sR7NB46V6BS2nKgQKIb-pB4bSJfuwjDQH4e8vRsPSUaDlsozlG3jY0-VEKEh4_3t7kfCHMTpxWoVehuil43zBQNTRTQJ-PoBBpnyrxlKtZQEa4WkDAih3zm1GuhcAOTXXmVcJeGLcLxJ6OEx6hvPqibtj3-NbyLGKfsNVpWD8K3qK8zNeoo2GRbdZFBARzGJ07PgtBGl33Pfttoyj7nv6YbPGlyi-0DcGArU1yuG7D-O0SLEUI_3DnK7ufkMiwuQhn0_Q9pZm5v0dS5OO55WH0HjfRtMISlqDh0MsRqfqBn5Whgbk-OZKjjZJNZAegp1ArU01EbV1hFTtAaEX-0pzYqqcl7wKMgxODhI1Lu26nkxZTGAdrrM7LpiBoxdRyTSqqFv5_JF8AwGnskNRfmqT-xDXxRKrdlD7m_krYn3HPcnO0Q3zQws_5SWb0GWk1K2npAxpiJDG2gHME8s7jgRKz_PYe6lpjkPPX_KetJW7xTWWmbbWOO6K8DLMkk4u3zrhL9nWPPT53q4kR_hvtxwWHY4ubnouDCP6m5SExU4K-Yf0MUF_DevuYt2BJTkiZ-Xl9cDbVDk2JlfF-7wbVAXka2lDlnMKbg1_PsY4NgVBvNCPxlTqmmFoAsSSHXebpJ6KT-m2OnOrh_Icly3tZfjktC1dIGX7Ora430JlsU6bU5tyeJ-tnGgh0BYcZ5iFSyig4NPw3syyUZZ7EfYhByPgTVpBd6bpqb-5_tPmBIN3xr_lD7Cq8iNeL5oz4ViUbXvzXoFzHSnRQJ6eqLUFm45MNPMxPzK86kCkTxJRjqZbNaMB25WCOJvNEHXmNgLQMDHR8QxN2xUoD7J5QXX_7hFC8XLRrJcQTB2MnwL6fXAldW0bIOFe_8R7wJ2Sc8_LT1ZOS5apHTMaYwepElpimy85NuCkikKd6fOwYh6GWjZnQV-LJA1lbuEG2je9NTZ7iGNtsDubWgJLAbu-2KdVUfoViXO1YPx8hcy9SZikC2kx6JQ8RppYFv99aieHtKE3k4PzagHbte7vUHWI52nNVCGRwc_FN35phHOMy_fjiSaiis77GRdMbA_dwS7yHdLlIYSTTsExSbfXCAA&state=cd04fd93-b688-4d07-91bb-3b15c6a9bd37&session_state=a8231a90-8f11-481b-954f-16dad6c81a69

Hello Luciano,

That's very strange.How many permissions are you giving in Azure? 

I think that the size of the token replied by Azure can be dependent on the number of permission associated to the access token ( Permissions to use outllook, calendar, graph, one drive and so on ).

Hi Miguel,

    I only requested the ones below

Hi All,

I'm having the same problem. Code parameter is too big in Azure response.

Anyone already what causes this ?

Thank you.

Best Regards,

Ricardo Pereira

Hi, 

Same problem here. Did anyone solve this? 

Thanks,
Roman

Hi, 

I have the same problem. Did anyone solve this?

Thanks,

Pier Paolo

I also happen to have this issue with some people. I'll try to look into it tomorrow and see if I can find the reason. 

I have the same problem also, if I cut the part of Code, then CallBack page loaded, but authorization code of Microsoft Login didn't valid.