Ontology (preview) item not visible in workspace despite being enabled in Admin Portal on F2 Capacit

[r_goda]

[Environment]

• Capacity (SKU): F2

• Home Region: Japan West

• Capacity Region: Japan East

[Issue] Even though all necessary settings in the Admin Portal are set to "Enabled," the "Ontology (preview)" item does not appear in the "+ New" > "Show all" menu within the workspace.

[Confirmed Admin Portal Settings] The following tenant settings are confirmed as "Enabled" (Applied to the entire organization):

• Users can create Ontology (preview) items: On

• Users can create Graphs (preview): On

• Users can create and share Data Agent item types (preview): On

• Users can use Copilot and other features powered by Azure OpenAI: On

• Data sent to Azure OpenAI can be processed outside your capacity's geographic region, compliance boundary, or national cloud instance: On

• Data sent to Azure OpenAI can be stored outside your capacity's geographic region, compliance boundary, or national cloud instance: On

[Questions] Are there any other required settings besides those listed above? Additionally, if the settings are correct, could any of the following be the cause of the item not appearing?

1. SKU Limitations: Is the Ontology feature not supported on entry-level capacities like F2, requiring a higher SKU such as F64?

2. Regional Limitations: Is it possible that the menu will not appear if the Home Region is outside the preview rollout target, even if it is enabled in the Admin settings?

3. Other Prerequisites: Are there any other mandatory settings or dependent features required to display the Ontology item?

If anyone has resolved a similar issue or has information regarding SKU-specific restrictions, I would greatly appreciate your guidance.

[benitovbreugel]

This really looks like something I have encountered today. 

I have 2 tenant and 2 fabric capacities. Both have all the preview items enabled, and I can create an ontology from scratch.
However for 1 capacity I can't create an ontology from the semantic model directly, see below:

Both capacities are in the same region, so it can't be that either. Still figuring out what it can be.....

[QLi]

Hi, have you found a solution? I have the exact same issue

[tayloramy]

Hi @r_goda, 

I'd recommend opening a ticket at this point. 

If you have a Pro license you can open a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi
Otherwise you can raise an issue at https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues. 

[tayloramy]

Hi @r_goda, 

That looks correct to me. Your workspace is correctly assigned, and all the tenant settings needed are correct. 

I wonder if there are some regional issues with the Japan capacities? 

After some digging, I did find that it is not available in Japan West, but you are in Japan East, which should support it. 

Fabric region availability - Microsoft Fabric | Microsoft Learn

Maybe because your home region is Japan West, it just doesn't work regardless of the location of your multi geo capacity? 

This feels very odd. 

[r_goda]

@tayloramy 

Thank you for taking the time to look into my issue. It’s a huge relief to know that my settings are correct, as this is my first time using Fabric and I was worried I might have missed something.

I also considered the possibility that the "multi-geo" setup might not be functioning correctly. As you pointed out, the home tenant region (Japan West) does not support "Ontology" and "Digital Twin Builder."

However, as shown in the attached image, "Digital Twin Builder" is visible in the "New item" list. Because of this, I believe that the multi-geo functionality itself is active and working.
" and "Digital Twin Builder."

[tayloramy]

Hi @r_goda, 

Once you enable all those settings, as long as your workspace is assigned to that F2 capacity, it should work. 

Can you verify that your workspace is assigned to the capacity and is not on a pro license? You can see this in the workspace settings under the license info tab. 

[r_goda]

Thank you for your reply. As shown in the image below, the capacity assigned to the workspace is definitely the F2 capacity. For your reference, I have also attached an image showing the "Analyze and train data" item under "NEW ITEM."

worlspace's capacityin newitem