Databricks Workspace in Trial Tier Causes Rate Limit of 0 Error — Assistance Needed

Problem description

I am experiencing an issue with my Azure Databricks workspace where I am encountering a rate limit of 0 error when trying to access certain features, specifically in the AI Playground, AI Functions, and AI Gateway. The workspace appears to be placed in a TRIAL_VERIFIED trust tier instead of a PAYABLE_VERIFIED tier, which I believe is causing the problem.

Environment

Azure Databricks workspace; region and SKU/tier not specified; no Azure Storage involved; no additional workload configuration provided.

What I've already tried

Environment:

• Azure Databricks workspace
• Exact region and workspace SKU/tier were not documented in the materials available for this summary
• No Azure Storage account read/write path was involved, according to the original report
• No notebook URL, library list, or additional workload-specific configuration was provided

What has been tried so far:

• At case creation, the customer documented the issue as ongoing and stated that it had never worked.
• The customer supplied workspace details privately in the original report.
• The customer confirmed that the scenario did not involve reading from or writing to Azure Storage.
• The customer pointed to a public community discussion describing a similar rate limit of 0 / temporary-disablement symptom and suggested that the workspace may have been placed in TRIAL_VERIFIED instead of PAYABLE_VERIFIED.
• No further email exchange, first-response troubleshooting notes, or additional reproduced test results were present in the case materials provided for this summary.
• The available guidance reviewed during the case did not include documented customer-facing instructions for changing a workspace trust tier or for clearing a Databricks-set rate limit of 0.
• Related public guidance reviewed during the case described similar 403 PERMISSION_DENIED behavior for Databricks-hosted premium model endpoints when the effective workspace rate limit is 0, but the case materials did not confirm that the same condition applies in this workspace.
• A diagnostic note associated with the workspace referenced preview-feature handling, but the materials did not confirm whether the affected capability in this report was a preview feature.

Where things stand now:

The most recent documented state is that the issue is ongoing, with no confirmed start time and no record in the provided materials of successful access.

The main gaps still visible from the case materials are:

• the exact Databricks feature or endpoint being accessed when the rate limit of 0 error appears;
• the full error text returned in this workspace, including whether it matches the 403 PERMISSION_DENIED / temporary-disablement wording seen in the referenced public discussion;
• the workspace's actual SKU/tier and region;
• whether the affected capability was generally available, preview, or otherwise access-limited at the time;
• whether the workspace was in fact classified as TRIAL_VERIFIED rather than PAYABLE_VERIFIED, or whether another workspace-level entitlement or quota setting produced the same symptom.

Current status

I am seeking assistance to understand why my workspace is in a trial tier and how to resolve the rate limit of 0 error to regain access to the affected features.