The provider's own All Apps tenant within VCF Automation. It lets the provider use its own capacity, run workflows through the built-in VCF Operations orchestrator, and share catalogue items and blueprints with other tenants.
Also called PCO.
Read more: Broadcom TechDocs
In the Ultra Transcenders books
Each book explains Provider Consumption Organization in context, with comparison tables and the common traps.
Terms in this definition
- Provider
The organisation that shares data in OpenSharing. Recipients also see a provider as a Unity Catalog securable, from which shares can be mounted as catalogs.
- ALL
A DAX function that ignores any filters and gives back every row of a table or every value of the named columns. Used within CALCULATE, it works as a modifier that clears filters, although REMOVEFILTERS states that intent more clearly where it is available.
- Tenant
A trusted, dedicated Microsoft Entra ID instance that stores the users, groups and app registrations of one organisation. A subscription trusts only a single tenant, although a tenant can be trusted by several subscriptions.
- VCF Automation
Self-service platform in VCF for provisioning VM, Kubernetes and AI workloads. Providers manage regions and tenants in one portal, while tenants handle projects and consumption in theirs.
- Capacity
A reserved block of compute for a tenant whose size is fixed by its SKU; Fabric F SKUs express it in capacity units (CUs). Workspaces assigned to it unlock features like Copilot, and from F64 upwards people with free licences can view Power BI content.
- Lakeflow Jobs
The orchestration product in Databricks, previously called Workflows. Each job contains at least one task, and the links between tasks make up a directed acyclic graph.
- VCF Operations orchestrator
Engine for running workflows, previously Aria Automation Orchestrator; VCF Automation relies on it to extend its capabilities and to connect to vSphere and further systems.
- Share
In OpenSharing, the container you fill with tables, views, volumes, models and notebooks for recipients. You need
CREATE SHAREon the metastore to make one; add a schema and all its assets, including later ones, go with history.