Microsoft Azure Traffic Manager Spoke
Summarize
Summary of Microsoft Azure Traffic Manager Spoke
The Microsoft Azure Traffic Manager Spoke allows ServiceNow customers to integrate their instances with Azure Traffic Manager for efficient DNS-based traffic distribution and load balancing. The latest version, v 2.0.0, was released on August 3, 2023, and requires an Integration Hub subscription.
Show less
Key Features
- Endpoint Management: Automate the creation, deletion, retrieval, and updating of Traffic Manager Endpoints.
- Profile Management: Create, delete, and update Traffic Manager Profiles, and check the availability of DNS names.
- Connection Management: Utilizes connection and credential aliases to streamline the management of multiple environments.
Key Outcomes
By integrating the Azure Traffic Manager Spoke, ServiceNow customers can efficiently manage DNS traffic, automate load-balancing tasks, and optimize performance across their applications. Ensure that the necessary dependencies and plugins are installed to facilitate smooth operation and leverage the full capabilities of the spoke.
Integrate ServiceNow instance with Azure Traffic Manager. Manage DNS-based traffic distribution and load balancing from your ServiceNow instance.
Request apps on the Store
Visit the ServiceNow Store website 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.
Integration Hub subscription
This spoke requires an Integration Hub subscription. For more information, see Legal schedules - IntegrationHub overview.
Spoke version
Azure Traffic Manager spoke v 2.0.0 is the latest version.
Supported versions
This spoke was built for Azure Traffic Manager 2022-04-01, but may be compatible with later versions.
Spoke requirements
Client ID and Client Secret of the Azure Traffic Manager registered in the Azure portal.
Spoke dependencies
- ServiceNow IntegrationHub Runtime (com.glide.hub.integration.runtime)
- ServiceNow IntegrationHub Action Step - REST (com.glide.hub.action_step.rest)
- Complex Object (com.glide.cobject)
- ServiceNow Flow Designer - Dynamic Inputs (com.glide.hub.dynamic_inputs)
- ServiceNow IntegrationHub Action Template - Data Stream (com.glide.hub.action_type.datastream)
- Azure Resource Management spoke (sn_azure_rm_spoke) v 2.0.0 is installed and a connection alias is created on your instance.
Spoke actions
The Azure Traffic Manager Spoke provides actions to automate DNS-based traffic load-balancing tasks when events occur in your ServiceNow instance. Available actions include:
| Category | Action | Description |
|---|---|---|
| Endpoint Management | Create Endpoint | Creates a Traffic Manager Endpoint. |
| Delete Endpoint | Deletes a Traffic Manager Endpoint. | |
| Look up Endpoint | Retrieves the details of a Traffic Manager Endpoint. | |
| Update Endpoint | Updates a Traffic Manager Endpoint. | |
| Profile Management | Create Profile | Creates a Traffic Manager Profile. |
| Delete Profile | Deletes a Traffic Manager Profile. | |
| Look up DNS Name Availability | Checks the availability of a Traffic Manager Relative DNS name. | |
| Look up Profile | Look up a Traffic Manager Profile. | |
| Look up Profiles by Resource Group | Look up Traffic Manager Profiles by Resource Group. | |
| Look up Profiles by Subscription ID | Look up Traffic Manager Profiles by Subscription ID. | |
| Update Profile | Updates a Traffic Manger Profile. |
Connection and credential alias requirements
Integration Hub uses aliases to manage connection and credential information. Using an alias eliminates the need to configure multiple credentials and connection information profiles when using multiple environments. If the connection or credential information changes, you don't need to update any actions that use the connection. For more information, see Connections and Credentials.
Set up the Microsoft Azure Traffic Manager Spoke
To execute the actions of the Microsoft Azure Traffic Manager Spoke, you must first install and configure the Microsoft Azure Resource Management Spoke. No separate configuration of the Microsoft Azure Traffic Manager Spoke is necessary. To view the procedure to set up the Microsoft Azure Resource Management Spoke, see Set up the Microsoft Azure Resource Management spoke.