Confirm small semantic model size max size on Microsoft documentation.

Eduardo Lourenço e Sá 0 Reputation points
2026-11-09T11:46:33.15+00:00

Reading the Large Semantic Storage Format documentation: https://learn.microsoft.com/en-us/fabric/enterprise/powerbi/service-premium-large-models?source=docs

It is confusing the reference to 1GB max size for semantic models.

  • In the first paragraph it is stated that in small semantic storage format, models have a limit of 1GB, "The default size limit is 1 GB"
  • But paragraph 3, starts with "While required for semantic models to grow beyond 10 GB, enabling the Large semantic model storage format has other benefits". This paragraph seems to in indicate that without Large Semantic model storage format, it's possible to have a semantic model of 10GB.

Can you clarify this point, and, if required, update the documentation so it's more confusing.

Azure Service Fabric
Azure Service Fabric

An Azure service that is used to develop microservices and orchestrate containers on Windows and Linux.

0 comments No comments

2 answers

Sort by: Most helpful
  1. Sedat SALMAN 14,535 Reputation points MVP
    2026-11-09T17:08:02.6833333+00:00

    Both statements are consistent. The 1 GB figure is the default limit. The 10 GB figure is the top of the small storage format range, and it applies only to larger SKUs. The Max Offline Semantic model Size setting defaults to 0, which means the highest limit defined by SKU. In small format that ceiling is SKU-specific. It is 1 GB on F2, 3 GB on F8, 6 GB on F32, and 10 GB on F64/P1 and above. Large storage format is not subject to that ceiling. Its limit is the capacity size or the maximum your admin sets. So 'required to grow beyond 10 GB' means small format tops out at 10 GB on the biggest SKUs. It does not mean every model can reach 10 GB. Pro workspaces on Reserved Capacity for Pro Workspaces stay at 1 GB. To suggest a wording change, use the feedback link at the bottom of the doc page. Which SKU are you on?

    References:

    If this solved it, please click Accept Answer and upvote so others with the same problem can find it.

    Was this answer helpful?

    0 comments No comments

  2. AI answer

    2026-11-09T11:46:49.7833333+00:00

    The documentation is distinguishing between the default limit, the small storage format hard ceiling, and what becomes possible after enabling large storage format.

    Supported clarification:

    • Default semantic model size limit is 1 GB.
    • For semantic models in small storage format (ABF), there is also an SKU-specific hard ceiling for Max Offline semantic model size. For example, F64/P1/A4 and higher listed SKUs up to F8192 have a 10 GB hard ceiling for small storage format.
    • For semantic models in large storage format (PremiumFiles), that small-format hard ceiling does not apply.
    • The statement “required for semantic models to grow beyond 10 GB” refers to moving past the small storage format ceiling. It does not mean every workspace without large storage format can always use 10 GB. The actual limit in small storage format depends on the SKU hard ceiling and capacity settings.

    So the correct interpretation is:

    1. 1 GB is the default size limit.
    2. In small storage format, the maximum can be higher than 1 GB depending on SKU and admin settings, but it is still capped by the SKU-specific hard ceiling.
    3. 10 GB is the small storage format hard ceiling for certain higher SKUs, not a universal limit for all semantic models.
    4. Large semantic model storage format must be enabled for a semantic model to exceed 10 GB.

    The wording is confusing because the first paragraph presents the default limit, while the later paragraph discusses the upper bound of small storage format on supported higher SKUs.


    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.