question

JamesGlover-4097 avatar image
2 Votes"
JamesGlover-4097 asked PramodValavala-MSFT commented

Logic App Office 365 Connector ARM Template Deployment

I currently deploy a Logic App and associated Office365 and Blob Storage connectors using ARM templates via Azure Devops. All these resources get deployed correctly, The only caveat is that the Office365 connector requires a manual "Authentication" step after deployment which we are fine with.

I've attached the template as "Template.txt" which is a JSON file.
15066-template.txt


When i view the connector in the Azure Portal, i require to authenticate which returns a success and displays as connected. The Logic app will still not receive any events from Office365.

What i then have to do is change the "Connected to" on the trigger in the logic app to a new connector, save the Logic App and then change it back and save and then it works.

1) Am i doing something wrong with the ARM template deployment?
2) Is this a bug with the Office365 Template connector?


azure-logic-apps
template.txt (19.9 KiB)
· 4
5 |1600 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Visible to all users

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

PramodValavala-MSFT avatar image PramodValavala-MSFT ·

It is possible that the trigger failed to setup because of the lack of authorization. Could you try to disable and re-enable the logic app after authorizing to see if that does the trick instead of changing the workflow itself?

One way to work around this behavior would be to use an API Connection resource already authorized, which can be directly used by newly created logic apps.

0 Votes 0 ·
JamesGlover-4097 avatar image JamesGlover-4097 PramodValavala-MSFT ·

Hi Pramod,

I've tried to enable and disable the logic application after deployment and this has not worked - Althought the API Connection get's deployed with this so this also might affect this test.

Is there a way to conditionally deploy the API Connector by detecting if it's already there before hand using the standard ARM deployment?

0 Votes 0 ·
PramodValavala-MSFT avatar image PramodValavala-MSFT JamesGlover-4097 ·

Could you confirm if you tried the disable/enable after authorizing the API Connection?

As for conditionally deploying a resource, the default deployment mode is the incremental mode which overwrites the properties matching the state in the template, which would remove secure properties as well. This can only be achieved by a separate script that checks for an existing connection before deploying it.



0 Votes 0 ·
Show more comments

0 Answers