Skip to content

A PowerShell script you can run to check all On-premises Data Gateways used by API connections

Notifications You must be signed in to change notification settings

joeshen117/connectionCheckerScript

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

7 Commits
 
 
 
 
 
 

Repository files navigation

On-premises Data Gateway checker script

This repository contains a PowerShell script you can run to list all On-premises Data Gateways used by Logic App API connections and save to a CSV file. For more information on finding correlations between Logic App API connections and On-premises Data Gateways, please visit my blog here.

Objective:

Find out which On-premises Data Gateways are used by which API connection resources.

Prerequisites:

Run the script:

After downloading the script into your machine, put in the name of your Azure subscription for the subscriptionName variable.

Then run the script and log into your Azure account in the pop-up window.

A CSV file named “output.csv” will be created in the same folder where the script resides.

The CSV file will contain all API connection resources along with the OPDGs they are using.

Columns:

  • connectionName: name of the API connection resource
  • connectionId: resource ID of the API connection
  • gatewayName: name of the On-premises Data Gateway resource
  • gatewatyId: resource ID of the On-premises Data Gateway

Notes:

  • If you encountered the "script not signed" error, please run the below PowerShell command to bypass the security policy in the current session.

    Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
  • Alternative to run the script locally, you may choose to run this through cloud shell. However please remember to remove the first command "Connect-AzAccount" as it will no longer be required.

About

A PowerShell script you can run to check all On-premises Data Gateways used by API connections

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published