Hi, It sounds like you're encountering an issue where the **OData query parameters** (such as `?$top=5`) are being stripped from the request when routed through the SAP OData connector via APIM. Additionally, the unexpected addition of a trailing slash (`/`) in the query path may be interfering with how SAP interprets the request. Here are a few things to check: 1. **Connector configuration**: Ensure that the `OdataQuery` parameter is explicitly defined and passed separately from the `relativePath`. Some connectors require query parameters to be set in a dedicated field rather than appended directly to the path. 2. **APIM rewrite policies**: Inspect the inbound and outbound policies in your APIM instance. It's possible that a rewrite or transformation policy is unintentionally modifying the URL structure or stripping query parameters. 3. **SAP OData endpoint behavior**: Some SAP services are sensitive to URL formatting. A misplaced slash or missing query string can lead to unexpected behavior or default responses. 4. **Reference documentation**: - SAP OData connector setup - Azure API Management policies - Martin's blog post #127881 — if available, this may contain specific guidance on OAuth2 and Principal Propagation. You might also consider logging the full request before it hits APIM to confirm whether the query string is present and correctly formatted. Thanks and best regards, Daniele **Note: This response was prepared with support from Copilot to ensure clarity and completeness.**