@kapa.ai How I can check the client id and client secrete and tenant id which I used while creating microsoft sharepoint source?

In Airbyte itself, the Microsoft SharePoint source configuration UI only stores these values; the docs you shared don’t describe any screen or API to re‑view the raw

client_id

,

client_secret

, or

tenant_id

once the source is created. The knowledge sources therefore don’t give a way to read them back from an existing SharePoint source. From the documentation, the only clearly documented ways to know these values are: 1. Look them up in Azure When you created the SharePoint (or related Microsoft Graph) application, Azure generated: - Application (client) ID - Directory (tenant) ID - Client secret You can re‑obtain them in the Azure Portal by going to your app registration under Azure Active Directory → App registrations, then: - `client_id`: shown as Application (client) ID - `tenant_id`: shown as Directory (tenant) ID - `client_secret`: under Certificates & secrets (only visible if you saved it or create a new one) [[SharePoint setup](https://docs.airbyte.com/integrations/sources/microsoft-sharepoint#step-1-set-up-sharepoint-application); [SharePoint Enterprise setup](https://docs.airbyte.com/integrations/enterprise-connectors/source-sharepoint-enterprise#step-1-set-up-sharepoint-application)]. 2. Check how they were originally collected For SharePoint and SharePoint Enterprise, the docs show that you manually enter Tenant ID, Client ID, and Client secret (or use OAuth) when creating the source, but they don’t document any way to later display those values from within Airbyte [[SharePoint step 2](https://docs.airbyte.com/integrations/sources/microsoft-sharepoint#step-2-set-up-the-microsoft-sharepoint-connector-in-airbyte); [SharePoint Enterprise step 2](https://docs.airbyte.com/integrations/enterprise-connectors/source-sharepoint-enterprise#step-2-set-up-the-microsoft-sharepoint-connector-in-airbyte)]. So, based on the available docs: - To verify which values you used, you’ll need to cross‑check the app registration in Azure (and/or your own password/secret manager where you stored them). - The knowledge sources do not document a way to read out those fields from an existing Airbyte source configuration.