---
title: Integrate PingIntelligence
description: After the policy deployment is complete, refer to the following topics for next steps:
component: pingintelligence
version: 5.1
page_id: pingintelligence:pingintelligence_integrations:pingintelligence_azure_integration_apis
canonical_url: https://docs.pingidentity.com/pingintelligence/5.1/pingintelligence_integrations/pingintelligence_azure_integration_apis.html
revdate: May 30, 2024
---

# Integrate PingIntelligence

After the policy deployment is complete, refer to the following topics for next steps:

It is recommended to read the following topics (part of the admin guides) apart from reading the [ASE](../api_security_enforcer/pingintelligence_ase.html) and [ABS AI Engine](../abs_ai_engine/pingintelligence_abs_ai_engine.html) Admin Guides:

* [Customizing ASE ports](../api_security_enforcer/pingintelligence_customizing_ase_ports.html)

* [API naming guidelines](../api_security_enforcer/pingintelligence_api_naming_guidelines.html)

* Adding APIs in [Sideband ASE](../api_security_enforcer/pingintelligence_sideband_ase.html). You can add individual APIs or you can configure a global API. For more information, see[API discovery and configuration](../abs_ai_engine/pingintelligence_api_discovery_configuration.html).

* [Configure ASE to ABS connectivity](../api_security_enforcer/pingintelligence_ase_to_abs_connectivity.html)

After you have added your APIs in ASE, the API model needs to be trained. The training of an API model is executed in the ABS AI engine. The following topics provide information on important topics, however it is a good practice to read the entire ABS Admin Guide.

* [AI engine training](../abs_ai_engine/pingintelligence_ai_engine_training.html)

* [API reports using Postman](../abs_ai_engine/pingintelligence_api_reports_using_postman.html)

* [Access PingIntelligence Dashboard](../pingintelligence_poc/pingintelligence_access_dashboard_docker_poc.html)