Skip to content

Commit d1cbc58

Browse files
committed
Fixing link
1 parent 880deee commit d1cbc58

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/automation/automation-connections.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -94,7 +94,7 @@ When you create your Automation account, it includes several global modules by d
9494

9595
## Adding a connection type
9696

97-
If your runbook or DSC configuration connects to an external service, you must define a connection type in a [custom module](shared-resources/modules.md#custom-cmdlets), called an integration module. This file specifies connection type properties and is named **<ModuleName>-Automation.json**, located in the module folder of your compressed **.zip** file. This file contains the fields of a connection that are required to connect to the system or service the module represents. Using this file, you can set the field names, data types, encryption status, and optional status for the connection type.
97+
If your runbook or DSC configuration connects to an external service, you must define a connection type in a [custom module](shared-resources/modules.md#custom-modules), called an integration module. This file specifies connection type properties and is named **<ModuleName>-Automation.json**, located in the module folder of your compressed **.zip** file. This file contains the fields of a connection that are required to connect to the system or service the module represents. Using this file, you can set the field names, data types, encryption status, and optional status for the connection type.
9898

9999
The following example is a template in the **.json** file format that defines user name and password properties for a custom connection type:
100100

0 commit comments

Comments
 (0)