Merge pull request #2742 from port-labs/PORT-12434-bug-clearly-state-that-service-accounts-token-are-not-supported-in-integrations

Bug PORT-12434 Add caution note regarding service account limitations for Ocean integrations

Author: sivanel97

docs/build-your-software-catalog/sync-data-to-catalog/sync-data-to-catalog.md

@@ -50,6 +50,19 @@ Below is a breakdown of the supported installation methods for Port integrations
 | **Self-hosted (Real-time)** | Managed entirely in your infrastructure. | 🟩⬜⬜⬜  | ✅<br/>(custom interval) | ✅ <br/>(Integration-dependent) | You provision, monitor, and maintain the integration. | Best for high-security or custom networking needs.|
 | **Scheduled (CI)**| Managed in your CI/CD environment. | 🟩🟩⬜⬜ | ✅ (custom interval) | ❌| Minimal infrastructure. You manage the CI/CD environment and triggers. | Best when real-time isn’t needed and you want full sync control. |
 
+
+:::caution Integration Service Account Limitation
+Service accounts (machine tokens) are currently not supported for Ocean integrations. This is a known limitation that affects:
+
+- **Audit/event logging functionality** - Service account tokens may not properly log events.
+- **Token validation** - Machine user tokens cannot be properly validated by the system.
+- **Some integration features** - May experience reduced functionality.
+
+**Current workaround**: Use personal or organizational credentials until this limitation is resolved.
+
+**Status**: This is being tracked as a feature request and will be addressed in a future release. For production environments requiring service account support, consider using Port-hosted integrations where available.
+:::
+
 ## Customize your integrations
 
 Now that you've installed an integration, let's see how you can customize it: