Microsoft Azure Functions discovery with Patterns
The Discovery and Service Mapping Patterns application uses the Azure - Functions (LP) and Azure - Functions TD Patterns to discover Azure Functions apps and map them in the context of application services. Discovering some of these resources may require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.
Request apps on the Store
Visit the ServiceNow Store to view all the available apps, and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the ServiceNow Store version history release notes.
Prerequisites
- Azure Functions detailed information
- Detailed information on products discovered by ITOM Visibility
- Azure service account
- Configure the Azure service account. For more information, see Set up a cloud account for Azure
- Azure Principal credentials
- On the ServiceNow AI Platform, create a service account for cloud discovery. Set the account Id to the Azure Service Principal as it appears at the Microsoft Azure Console. For more information see: Create Azure cloud credentials
- Privileges
- On the Microsoft Azure Console, provide a user with the API Management Service Reader role.
- Run Azure Cloud discovery
- For detailed information, see: Discovery for Microsoft Azure
- Create discovery schedule
- Create a discovery schedule in Cloud Discovery Workspace
Data collected by Discovery during horizontal discovery
| Table and field | Description |
|---|---|
| Azure Function [cmdb_ci_cloud_function] | |
| name | The name of the Function app. |
| Object_id | The ID of the Function app. |
| ip_address | The IP Address of the Function app. |
| fqdn | The Fully Qualified Domain Name (FQDN) of the Function app. |
| code_location_url | The URL of the Function app source code. |
| app_function_state | The state of the Function app. |
| operational_status | The operational status of the Function app. |
| install_status | The installation status of the Function app. |
CI relationships
These relationships are created to support Azure Functions discovery:
| CI | Relationship | CI |
|---|---|---|
| Azure Functions [cmdb_ci_cloud_function] | Hosted on::Hosts | Azure datacenter [cmdb_ci_azure_datacenter] |
Connections found by Service Mapping during top-down discovery
Service Mapping can discover the following connections:
- Connections to the following databases: MSSql, MySql, MongoDB, and Documentum.
- HTTP connections belonging to Azure Functions environment, for example, https://scenario4-hop1-azure-function.azurewebsites.net. Remarque :Service Mapping does not scan java classes/jars and binary files for possible information about outgoing HTTP connections of Azure Functions. If java classes/jars and binary files are the only source of information about some outgoing HTTP connections, Service Mapping does not find such HTTP connections.