We are evaluating the SharePoint Online integration generated by Integration Builder in an OutSystems 11 self-managed environment. The development environment is not publicly reachable. The use case is to upload an existing PDF from an OutSystems application to a SharePoint Online document library.
I would like to distinguish integration creation and deployment from runtime file upload:
When creating and publishing the integration, what connectivity is required between Integration Builder and the OutSystems development environment? The network requirements mention the environment’s public DNS hostname. Is there a supported approach when the development environment is not publicly reachable? After deployment to another environment through LifeTime, which connection-configuration or maintenance operations, if any, require connectivity to Integration Builder?
At runtime, when a generated Server Action uploads the PDF, which outbound FQDNs and ports must the OutSystems environment reach? Please include any destinations needed for authentication as well as file upload. Is allowing outbound HTTPS on TCP 443 to the SharePoint tenant sufficient?
Where are the target SharePoint site, document library, and folder specified: during integration creation, in Integration Manager, or as Server Action inputs? What URL or identifier format is required, and how can the configured value be checked for each environment?
In particular, I want to avoid confusing the SharePoint location where the PDF is stored with the network destinations that must be allowed through the firewall. References to OutSystems documentation or a configuration example would be appreciated.
For the dev/design-time side: per the docs, every environment you connect to Integration Builder (dev included) needs inbound+outbound HTTPS 443 with integrationbuilder.outsystems.com, and it talks to it via the environment's public DNS hostname - so there's no supported route if the dev environment isn't publicly reachable.
https://success.outsystems.com/documentation/11/integration_with_external_systems/create_connectors_with_integration_builder/how_to_set_up_integration_builder/
Once an integration is deployed via LifeTime, that target environment doesn't need its own connection to Integration Builder unless you want auto-created connections or the email-based connection request flow - manual connection setup in Integration Manager works fine without connectivity to Integration Builder itself.
For runtime, the SharePoint Online integration doc only specifies outbound HTTPS 443 "to your SharePoint Online service" - it doesn't list exact FQDNs, so for a locked-down firewall I'd lean on Microsoft's own published SharePoint Online/Graph endpoint ranges (or a packet capture during a test call) rather than a single hardcoded hostname.
https://success.outsystems.com/documentation/11/integration_with_external_systems/create_connectors_with_integration_builder/use_integration_builder/sharepoint_online_integration/
Thank you for your responce.This clearly separates the design-time and runtime requirements, and confirms that only the development environment needs connectivity to Integration Builder. We will confirm the exact runtime endpoints with OutSystems Support and Microsoft's published endpoint information. Thanks again for the helpful references.