- Knowledge Base
- Technical Area
- Integration Proxy
-
Customer Portal
-
Benefit Forms
-
Revenues Forms
-
Editing Forms
-
Customer Engagement Centre (Previously known as CSVu)
-
Blue Badge and Concessionary Travel
-
Built Environment
-
BACAS
-
Health (CHC)
-
Events
-
General Form Guidance
-
Technical Area
-
Open Process
-
Forms
-
Waste Services
-
'How to...' Sessions
-
Awards and Grants
-
Social Care Financial Assessments
-
Tender Responses - General
-
IEG4 Team Updates
-
Internal Process Guides
-
Public Protection
-
Local Land Charges
What ports and protocol does the Hybrid Connection Manager need?
To support the Hybrid Connections that Hybrid Connection Manager (HCM) is configured for, the HCM requires:
- TCP access to Azure over port 443.
- TCP access to the Hybrid Connection endpoint.
- The ability to do DNS look-ups on the endpoint host and the Azure Service Bus namespace.
The endpoint host is the on-premise machine that represents the final destination for the network call being made. This would typically be machine that hosts the API's to support back office integration.
The Azure Service Bus namespace will be unique to each customer and represents the Azure side of the connection. This address usually takes the format <customer>.servicebus.windows.net