Legacy Dev Forum Posts

 View Only

Sign Up

OAuth for Microsoft Power Apps

  • 1.  OAuth for Microsoft Power Apps

    Posted 06-05-2025 18:21

    carlos.camacho | 2022-02-05 10:48:56 UTC | #1

    Hi guys,

    We are currently trying to create an application (PowerAutomate) within CRM Dynamics 365 that will allow us to perform the upload of a contact list.

    The problem I have is when linking the OAuth between Genesys Cloud and Dynamics 365.

    In Genesys Cloud the configuration I do is as follows:

    Grant Types: Code Authorization Authorized redirect URIs (one per line): https://global.xxxxx.azure-apim.net/redirect (generated by default by Azure) Scope: outbound and outbound:readonly Authorization URL: Automatically generated by Genesys. (Genesys Cloud Admin) ClientID: Automatically generated by Genesys. Client Secret: Automatically generated by Genesys.

    From Dynamics 365 (PowerAutomate) I have tried several combinations and none has worked, I attach one of them:

    Identity Provider: Generic OAuth 2 ClientID: The one generated by Genesys Cloud before. ClientSecret: The one generated by Genesys Cloud before. Authorization URL: I tested both the URL generated for me by Genesys Cloud (Genesys Cloud Admin) and https://apps.mypurecloud.de/oauth/token TokenURL: I have tested with https://apps.mypurecloud.de/oauth/token RefreshURL: I have tested with https://apps.mypurecloud.de/oauth/token Scope: outbound and outbound:readonly Redirect URL: https://global.xxxxx.azure-apim.net/redirect (generated by default by Azure)

    With this configuration we have come to get the same error message you had, Invalid Redirect URL.

    It seems to be an OAuth configuration problem, could you give me a hand to solve it?

    Thanks in advance. Best regards.


    Trystan | 2022-02-08 03:00:53 UTC | #2

    Hi Carlos I was able to connect using OAuth2 & Power Automate, I just used the generic HTTP post request which looks like this


    carlos.camacho | 2022-02-08 10:08:29 UTC | #3

    Hello Trystan,

    First of all thanks for your answer, we have that way of doing it under control and it works correctly, however, we were looking to do something "less manual".

    What we propose to do is:

    • Save the clientid and clientsecret and the current token in an Azure keyvault.
    • The token is accessed from dataverse with a secure environment variable (and can be used in flow, etc...).
    • And an Azure function renews the token periodically.

    Any idea about how to do this?

    Regards.


    system | 2022-03-11 10:08:55 UTC | #4

    This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.


    This post was migrated from the old Developer Forum.

    ref: 13471