Office
A suite of Microsoft productivity software that supports common business tasks, including word processing, email, presentations, and data management and analysis.
1,733 questions
How do I grant my logic app sitting on internal asev3 Office365 api inbound traffic
Ulysses Grant, IV
0
Reputation points
I have a logic app sitting in an internal ase which is also sitting behind an azure app gateway. The logic app does not automatically "fetch" via the run trigger I assume due to some traffic constraints utilizing the office365 api connection on an internal ase. Is the best way to accomplish this is to utilize a NSG to allow inbound/outbound traffic to the various list of ip address etc for Office365? Are there any pre-existing service tags I can use on the NSG?
Office
Azure Logic Apps
Azure Logic Apps
An Azure service that automates the access and use of data across clouds without writing code.
3,223 questions
{count} votes
-
MayankBargali-MSFT 70,556 Reputation points2023-01-19T09:53:16.8433333+00:00 @Ulysses Grant, IV If you are using Azure connector then you can use Azure connector service tag for your inbound traffic as the any trigger connector will try to make a call to your workflow and if it is under the secure network/no internet access then your workflow will not be triggered. So your Azure connector IP should be whitelisted or use the service tag which should help you in triggering your office 365 connector.
-
Ulysses Grant, IV 0 Reputation points
2023-01-20T04:55:19.9633333+00:00 @MayankBargali-MSFT So I've added the Azure Connector service tag to the NSG that is associated to the internal ASE but still not getting a "real-time" response from the "when email arrives" trigger on the logic app. Are you saying this is due to no internet access? I saw a "internet" service tag as well but not sure if this is efficient.
-
MayankBargali-MSFT 70,556 Reputation points
2023-01-24T05:54:11.07+00:00 @Ulysses Grant, IV When you are using Azure connectors then communication happens via the internet. In case of any trigger the connector IP's will try to trigger your workflow and if your workflow is under restricted network/no internet on the machine then it will not be able to trigger your workflow. I am not sure if Internet tag would help as I haven't tested the setup but as per the document the traffic to/from Internet and allow traffic to/from AzureCloud or other available service tags of specific Azure services so it should work.
Sign in to comment
Sign in to answer