# February 2026

> The Database Hub connector now sends the User-Agent identifier `uipath+uipath` with every API request to Databricks. This helps Databricks and administrators attribute requests in logs and during troubleshooting. No changes to authentication or activities are required.

## February 23, 2026

### Database Hub updates

#### New UiPath identifier sent with Databricks requests

The Database Hub connector now sends the User-Agent identifier `uipath+uipath` with every API request to Databricks. This helps Databricks and administrators attribute requests in logs and during troubleshooting. No changes to authentication or activities are required.

### GitHub updates

#### Improvements

We improved the error messaging on invalid organization ID during connection creation and update.

#### Bug fixes

* Repository lookup did not render for issue-related triggers.
* Incorrect values were displayed in the **Create Branch** activity for **Branch SHA**, causing the activity to fail. The lookup base branch SHA has been updated to refer to the correct SHA endpoint.

### OpenAI V1 Compliant updates

#### Support for HTTP Request activity

The **HTTP Request** activity is now available for the OpenAI V1 Compliant LLM connector. This activity allows you to go beyond the predefined activities in a given package and make requests to any endpoint of a vendor's API.

HTTP Request reuses the connector pre-configuration and provides transparency of headers, authentication, and query parameters. You can reuse any of your connections, and provide the endpoint and the JSON payload. Use this connector-specific **HTTP Request** activity to benefit from Integration Service's capabilities for connection management. To learn more, refer to the [HTTP Request activity](https://docs.uipath.com/activities/other/latest/integration-service/http-request-activity) page.

#### Improvements

* We improved the guidance on filling in the URL field on the connection creation page to clarify that the entire address including `https://` is required.
* We made a few updates to the order, labels, and tooltips of the options available on the connection page and in the Generate Chat Completion activity.

### Anthropic Claude bug fixes

Characters were not properly masked in the **API key** field of the connection creation page.

### AWS Bedrock bug fixes

Characters were not properly masked in the **API key** field of the connection creation page.

### Google Vertex bug fixes

* Authentication was unsuccessful when using the HTTP Request activity.
* Characters were not properly masked in the **Service account key** field of the connection creation page.

### Google Vision bug fixes

Characters were not properly masked in the **Service account key** field of the connection creation page.

### Jira bug fixes

Optional scopes were listed under custom scopes instead of predefined scopes on the connection creation page.

## February 17, 2026

### Expanded data residency for UiPath GenAI Activities

We are expanding data residency support for UiPath GenAI Activities in several new regions: Canada, the European Union, India, Singapore, the United Kingdom, and the United States. Data is now stored and processed within the selected regions, helping you meet local regulatory requirements while maintaining high availability and security.

For more information, refer to [Data residency](https://docs.uipath.com/automation-cloud/automation-cloud/latest/admin-guide/data-residency-cloud#global-cloud-regions) in the Automation Cloud admin guide.

## February 13, 2026

### Removed activities and triggers

The following activities and triggers are no longer available in the **Microsoft OneDrive & SharePoint**, **Microsoft Outlook 365**, **Gmail**, **Google Drive**, and **Google Sheets** connectors for new automations:

#### Activities

* **List All Records**
* **Get Record**
* **Insert Record**
* **Update Record**
* **Delete Record**

#### Triggers

* **New Record Created**
* **Existing Record Updated**
* **Existing Record Deleted**

This change affects only new automations. Existing workflows that use these generic activities or triggers will continue to run as before.

:::note
As an exception for the Microsoft Outlook 365 connector, the [List All Records](https://docs.uipath.com/activities/other/latest/productivity/office365-list-all-records) activity remains available only for the Attachment object, and supports the use case of downloading all email attachments.
::::

Alternatively, if a required operation is not available through the out-of-the-box activities of the connector, you can use the correspondent HTTP Request activity to call the underlying service APIs. This action enables custom or currently unsupported scenarios while maintaining full API flexibility.

## February 10, 2026

### Expanded data residency in Australia and Japan for UiPath GenAI Activities

We are expanding data residency support in Australia and Japan for UiPath GenAI Activities. Data is now stored and processed within the selected regions, helping you meet local regulatory requirements while maintaining high availability and security.

For more information, refer to [Data residency](https://docs.uipath.com/automation-cloud/automation-cloud/latest/admin-guide/data-residency-cloud#global-cloud-regions) in the Automation Cloud admin guide. 

## February 9, 2026

### New authentication method for the Microsoft Azure OpenAI connector

A new authentication method, **OAuth 2.0 Client credentials**, is now available for the Microsoft Azure OpenAI connector. This method provides a more secure way to authenticate and authorize access to the Azure OpenAI services using your client credentials.

### Bug fixes

* Workday REST connection creation was unsuccessful for certain account types.
* ServiceNow connection creation could be unsuccessful if the client secret contained special characters.
* Jira connection creation sometimes failed when the Basic authentication type was used.
* Characters were not properly masked in the **API key** field of the connection creation page for the Open AI and Azure Open AI connectors.
