Configure button for Microsoft Azure DevOps Boards spoke inbound connection does not respond in Flow Designer<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Issue: When setting up the Microsoft Azure DevOps Boards spoke inbound connection in Flow Designer on a domain-separated instance, selecting the Configure button results in no action or response. Root Cause: When a spoke is installed in a domain-separated instance, the spoke configuration files are placed inside the Global Domain to ensure all tenants down the domain hierarchy can inherit and access the integration logic. However, if your user profile is scoped to a non-Global domain (such as Default Domain), a domain scope mismatch prevents you from activating or configuring the endpoint. The Configure button does not respond because the application scope does not align with the spoke's configuration files location i.e Global Domain.Resolution:When configuring the Microsoft Azure DevOps Boards External Trigger endpoint in a domain-separated instance, ensure the following scope settings are correctly configured: Set your domain scope to Global.Set your application scope to Microsoft Azure DevOps Boards Spoke (or the spoke-specific application scope for the spoke you are configuring).Navigate to All → Process Automation → Workflow Studio.Click the Integrations tab.In the left panel, click on Inbound connections.Locate the Microsoft Azure DevOps Boards spoke endpoint and click View Details.Click Configure on the External Trigger endpoint. It opens a pop up where user can select the User who can trigger the endpoint and click Activate.Copy and store the generated token, URL, and header parameter name for use in your Microsoft Azure DevOps configuration. Best practice for domain-separated environments:When working with spokes, always apply the following scope configuration: Domain scope: GlobalApplication scope: Spoke-specific (for example, Microsoft Azure DevOps Boards Spoke) This isolation protects the spoke's core files from accidental modification or corruption by other platform components and ensures proper inheritance across the domain hierarchy.