You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/build-your-software-catalog/sync-data-to-catalog/cloud-providers/azure/resource_templates/advanced.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,12 +31,12 @@ import KeyVaultBlueprint from './key_vault/\_blueprint.mdx'
31
31
import KeyVaultAppConfig from './key_vault/\_port_app_config.mdx'
32
32
33
33
34
-
## Mapping Storage Resources
34
+
## Mapping storage resources
35
35
36
36
The following example demonstrates how to ingest your Azure Storage Accounts and Containers to Port.
37
37
You can use the following Port blueprint definitions and integration configuration:
38
38
39
-
:::note
39
+
:::note Resource group requirement
40
40
The Storage Account has a relation to the Resource Group, so creation of the [Resource Group blueprint](#mapping-resource-groups) is required.
41
41
:::
42
42
@@ -51,12 +51,12 @@ Here are the API references we used to create those blueprints and app config:
The following example demonstrates how to ingest your Azure Database Resources to Port.
86
86
You can use the following Port blueprint definitions and integration configuration:
87
87
88
-
:::note
88
+
:::note Resource group requirement
89
89
The Database Resources below have a relation to the Resource Group, so creation of the [Resource Group blueprint](#mapping-resource-groups) is required.
90
90
:::
91
91
@@ -97,12 +97,12 @@ Here are the API references we used to create those blueprints and app config:
The following example demonstrates how to ingest your Azure Service Bus resources (Namespaces, Queues, Topics, and Subscriptions) to Port.
103
103
You can use the following Port blueprint definitions and integration configuration:
104
104
105
-
:::note
105
+
:::note Hierarchical relationships
106
106
The Service Bus resources have a hierarchical relationship. The Namespace relates to the Resource Group, Queues and Topics relate to the Namespace, and Subscriptions relate to Topics. Creation of the [Resource Group blueprint](#mapping-resource-groups) is required.
107
107
:::
108
108
@@ -123,12 +123,12 @@ Here are the API references we used to create those blueprints and app config:
123
123
-[Service Bus Topic](https://learn.microsoft.com/en-us/rest/api/servicebus/stable/topics/list-by-namespace)
124
124
-[Service Bus Subscription](https://learn.microsoft.com/en-us/rest/api/servicebus/stable/subscriptions/list-by-topic)
125
125
126
-
## Mapping Application Insights
126
+
## Mapping application insights
127
127
128
128
The following example demonstrates how to ingest your Azure Application Insights components to Port.
129
129
You can use the following Port blueprint definitions and integration configuration:
130
130
131
-
:::note
131
+
:::note Resource group requirement
132
132
Application Insights has a relation to the Resource Group, so creation of the [Resource Group blueprint](#mapping-resource-groups) is required.
133
133
:::
134
134
@@ -140,12 +140,12 @@ Here are the API references we used to create those blueprints and app config:
0 commit comments