Skip to content

Commit 482b12b

Browse files
committed
change h3 to h4
1 parent 7c2c157 commit 482b12b

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/service-connector/how-to-build-connections-with-iac-tools.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ The following sections show how to create a web app and a storage account and co
4545

4646
### Provision source and target services
4747

48-
### Authoring from scratch
48+
#### Authoring from scratch
4949

5050
Authoring the template from scratch is the preferred and recommended way to provision source and target services, as it's easy to get started and makes the template simple and readable. Following is an example, using a minimal set of parameters to create a webapp and a storage account.
5151

@@ -110,15 +110,15 @@ resource storageAccount 'Microsoft.Storage/storageAccounts@2023-01-01' = {
110110
}
111111
```
112112

113-
### Export and polish
113+
#### Export and polish
114114

115115
If the resources you're provisioning are exactly the same ones as the ones you have in the cloud, exporting the template from Azure might be another option. The two premises of this approach are: the resources exist in Azure and you're using ARM templates for your IaC. The `Export template` button is usually at the bottom of the sidebar on Azure portal. The exported ARM template reflects the resource's current states, including the settings configured by Service Connector. You usually need to know about the resource properties to polish the exported template.
116116

117117
:::image type="content" source="./media/how-to/export-webapp-template.png" alt-text="Screenshot of the Azure portal, exporting arm template of a web app.":::
118118

119119
### Build connection logic
120120

121-
### Using Service Connector and storing configuration in App Configuration
121+
#### Using Service Connector and storing configuration in App Configuration
122122

123123
Using the App Configuration to store configuration naturally supports IaC scenarios. We therefore recommend you use this method to build your IaC template if possible.
124124

@@ -158,7 +158,7 @@ resource serviceConnector 'Microsoft.ServiceLinker/linkers@2022-05-01' = {
158158
}
159159
```
160160

161-
### Using Service Connector
161+
#### Using Service Connector
162162

163163
Creating connections between the source and target service using Service Connector is the preferred and recommended way if the [Service Connector ](./known-limitations.md)[IaC limitation](./known-limitations.md) doesn't matter for your scenario. Service Connector makes the template simpler and also provides additional elements, such as the connection health validation, which you won't have if you're building connections through template logic directly.
164164

@@ -202,7 +202,7 @@ For the formats of properties and values needed when creating a Service Connecto
202202

203203
:::image type="content" source="./media/how-to/export-sc-template.png" alt-text="Screenshot of the Azure portal, exporting arm template of a service connector resource.":::
204204

205-
### Using template logic
205+
#### Using template logic
206206

207207
For the scenarios where the Service Connector [IaC limitation](./known-limitations.md) matters, consider building connections using the template logic directly. The following template is an example showing how to connect a storage account to a web app using a system-assigned identity.
208208

0 commit comments

Comments
 (0)