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
+78-6Lines changed: 78 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,13 +18,25 @@ import WebAppBlueprint from './compute_resources/\_web_app_blueprint.mdx'
18
18
import DatabaseAppConfig from './database_resources/\_port_app_config.mdx'
19
19
import PostgresFlexibleServerBlueprint from './database_resources/\_postgres_flexible_server_blueprint.mdx'
20
20
21
+
import ServiceBusNamespaceBlueprint from './service_bus/\_service_bus_namespace_blueprint.mdx'
22
+
import ServiceBusQueueBlueprint from './service_bus/\_service_bus_queue_blueprint.mdx'
23
+
import ServiceBusTopicBlueprint from './service_bus/\_service_bus_topic_blueprint.mdx'
24
+
import ServiceBusSubscriptionBlueprint from './service_bus/\_service_bus_subscription_blueprint.mdx'
25
+
import ServiceBusAppConfig from './service_bus/\_port_app_config.mdx'
21
26
22
-
## Mapping Storage Resources
27
+
import ApplicationInsightsBlueprint from './application_insights/\_blueprint.mdx'
28
+
import ApplicationInsightsAppConfig from './application_insights/\_port_app_config.mdx'
29
+
30
+
import KeyVaultBlueprint from './key_vault/\_blueprint.mdx'
31
+
import KeyVaultAppConfig from './key_vault/\_port_app_config.mdx'
32
+
33
+
34
+
## Mapping storage resources
23
35
24
36
The following example demonstrates how to ingest your Azure Storage Accounts and Containers to Port.
25
37
You can use the following Port blueprint definitions and integration configuration:
26
38
27
-
:::note
39
+
:::note Resource group requirement
28
40
The Storage Account has a relation to the Resource Group, so creation of the [Resource Group blueprint](#mapping-resource-groups) is required.
29
41
:::
30
42
@@ -39,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.
74
86
You can use the following Port blueprint definitions and integration configuration:
75
87
76
-
:::note
88
+
:::note Resource group requirement
77
89
The Database Resources below have a relation to the Resource Group, so creation of the [Resource Group blueprint](#mapping-resource-groups) is required.
78
90
:::
79
91
@@ -85,6 +97,66 @@ 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
+
You can use the following Port blueprint definitions and integration configuration:
104
+
105
+
:::note Hierarchical relationships
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
+
:::
108
+
109
+
<ServiceBusNamespaceBlueprint/>
110
+
111
+
<ServiceBusQueueBlueprint/>
112
+
113
+
<ServiceBusTopicBlueprint/>
114
+
115
+
<ServiceBusSubscriptionBlueprint/>
116
+
117
+
<ServiceBusAppConfig/>
118
+
119
+
Here are the API references we used to create those blueprints and app config:
120
+
121
+
-[Service Bus Namespace](https://learn.microsoft.com/en-us/rest/api/servicebus/stable/namespaces/list-by-subscription)
122
+
-[Service Bus Queue](https://learn.microsoft.com/en-us/rest/api/servicebus/stable/queues/list-by-namespace)
123
+
-[Service Bus Topic](https://learn.microsoft.com/en-us/rest/api/servicebus/stable/topics/list-by-namespace)
124
+
-[Service Bus Subscription](https://learn.microsoft.com/en-us/rest/api/servicebus/stable/subscriptions/list-by-topic)
125
+
126
+
## Mapping application insights
127
+
128
+
The following example demonstrates how to ingest your Azure Application Insights components to Port.
129
+
You can use the following Port blueprint definitions and integration configuration:
130
+
131
+
:::note Resource group requirement
132
+
Application Insights has a relation to the Resource Group, so creation of the [Resource Group blueprint](#mapping-resource-groups) is required.
133
+
:::
134
+
135
+
<ApplicationInsightsBlueprint/>
136
+
137
+
<ApplicationInsightsAppConfig/>
138
+
139
+
Here are the API references we used to create those blueprints and app config:
The resources in this page are only few of the resources that the Azure Exporter supports.
90
162
If you don't find the Azure resource you want to map to Port head to the [Mapping Extra Resources](/build-your-software-catalog/sync-data-to-catalog/cloud-providers/azure/resource_templates/mapping_extra_resources.md) page to learn about what kind of azure resources are supported by the Azure integration and how to map them into Port.
0 commit comments