When chatting with the Gemini Enterprise assistant, users can attach files using the file picker. The assistant supports three file sources: Local files, files from Google Drive, and files from Microsoft OneDrive. This page describes how administrators configure this behavior.
If you want end users to select files from Google Drive and OneDrive, you can control how end users sign in by reusing the data store configuration that you set up when configuring Google Drive data store and OneDrive data store. This gives you control over the following:
- Which sign-in app the picker uses. A picker can reuse the Microsoft Entra (formerly Azure AD) or Google application that you configure on the connector instead of the default Google-managed application.
- Which Microsoft Entra tenant the OneDrive picker uses. The OneDrive picker can sign users in against your specific Microsoft Entra tenant.
For the end-user experience of attaching and chatting about files, see Upload and chat about files.
How file pickers work
If you configured your Google Drive and OneDrive data stores to use the same authorization configurations for the file picker, the file picker uses the same settings to authenticate users. The following table summarizes the two controls and the pickers they affect.
| Control | What it does | Applies to |
|---|---|---|
| Custom sign-in app | To authenticate users when they attach files to the assistant using the file picker, Gemini Enterprise can use your data store's existing Microsoft Entra ID or Google Identity configurations instead of the default Google-managed application. | Google Drive and OneDrive |
| Tenant enforcement | The OneDrive picker requires users to sign in against your specific
Microsoft Entra tenant (https://login.microsoftonline.com/{your-tenant}/...)
instead of the shared sign-in endpoint (/common/), so that
users from other tenants can't authenticate. The tenant is read from the
attached OneDrive connector. |
OneDrive only |
Administrators attach connectors to an app to configure this behavior.
When you designate a configuration provider, the following rules apply:
- One provider per connector type. You can attach only one OneDrive configuration provider and one Google Drive configuration provider to an app at a time. Marking a second connector of the same type as a provider is rejected with an invalid-argument error.
- The provider must be an action-enabled connector. The configuration provider must be a OneDrive or Google Drive connector that supports actions or federated access. An ingestion-only connector can't be a configuration provider. For more information, see Manage actions.
Before you begin
Confirm the following before you configure the file pickers:
- Administrator access.
Grant the Discovery Engine Editor role (
roles/discoveryengine.editor). This role is required for the user to create the data store. To grant this role, do the following:- In the Google Cloud console, go to the IAM page.
- Locate the user account and click edit Edit.
- Grant the
Discovery Engine Editorrole to the user. For more information, see IAM roles and permissions.
- Custom OneDrive sign-in app. Ensure you have a Microsoft Entra ID application that you control, including its client ID, client secret, and tenant ID, and a OneDrive account within that tenant for testing. For more information, see Register an application with the Microsoft identity platform.
- Configured data store. Configure a OneDrive data store or Google Drive data store. When configuring the data store, you configure the authentication settings that include the client ID and client secret, and tenant ID for the OneDrive data store. For more information, see:
- Attached data store. Attach the OneDrive data store or Google Drive data store to your Gemini Enterprise app. For more information, see Connect a data store to an app.
Use your own sign-in app
By default, the picker uses the Google-managed application for sign-in. You can make the picker use your own Microsoft Entra ID or Google Identity instead by designating one connector as the picker's configuration provider.
If you already have a configured OneDrive or Google Drive data store, follow these steps:
In the Google Cloud console, go to the Gemini Enterprise page.
Select or create a Google Cloud project.
In the navigation menu, click Data stores.
Search for your data store, and click the name of the data store.
Click View/Edit parameters.
Select the Picker Config Provider option.
Click Save.
Revert changes to use the Google-managed application
To return to using the default Google-managed application for file picker authentication, follow these steps:
In the Google Cloud console, go to the Gemini Enterprise page.
Select your Google Cloud project.
In the navigation menu, click Data stores.
Click the name of your data store.
Click View/Edit parameters.
Clear the Picker Config Provider field.
Click Save.
End-user experience
After you configure the pickers, end users have the following experience:
- For OneDrive, users are prompted to sign in to your organization's Microsoft tenant. Accounts from other tenants are turned away.
- Sign-in uses whichever application you configured: the Google-managed application by default, or your own application if you set a configuration provider.
- After the first successful sign-in, the connection is remembered for subsequent file selections.
For more information about the end-user experience, see Upload and chat about files.
Troubleshooting
| Symptom | Likely cause | Resolution |
|---|---|---|
Marking a connector as a **Picker Config Provider** fails with
Cannot enable picker_config_provider on data connector '...'
because another connector in the same engine is already the picker config
provider: '...'. An engine can have at most one picker_config_provider
connector; disable it on the other connector first. |
Another connector in the same engine is already the picker config provider. An engine can have at most one. | Clear the **Picker Config Provider** parameter on the other connector, and then retry. |
OneDrive sign-in fails with AADSTS50020: User account
'user@domain.com' from identity provider '...' does not exist in tenant
'...' |
The user's account is in a different Microsoft Entra tenant than the tenant configured on the connector. The tenant-specific sign-in endpoint rejects the account. | Tenant enforcement works as intended. Have the user sign in with an account in your configured tenant, or update the connector's tenant ID. |
| OneDrive still prompts the shared sign-in endpoint. | The tenant isn't configured yet, or the change hasn't propagated. | Confirm the connector's tenant ID. Configuration changes can take up to about 3 minutes to take effect; wait and then retry. |
What's next
- Set up the Microsoft OneDrive connector.
- Set up the Google Drive connector.
- Learn about the end-user experience in Upload and chat about files.