Notikumi
Power BI DataViz pasaules čempionāts
14. febr. 16 - 31. marts 16
Ar 4 iespējām piedalīties, jūs varētu laimēt konferences paketi un iekļūt LIVE Grand Finale Lasvegasā
Uzzināt vairākŠī pārlūkprogramma vairs netiek atbalstīta.
Jauniniet uz Microsoft Edge, lai izmantotu jaunāko līdzekļu, drošības atjauninājumu un tehniskā atbalsta sniegtās priekšrocības.
Piezīme
This article forms part of the Power BI implementation planning series of articles. This series focuses primarily on the Power BI experience within Microsoft Fabric. For an introduction to the series, see Power BI implementation planning.
This tenant setup article introduces important aspects to know about setting up your Fabric tenant, with an emphasis on the Power BI experience. It's targeted at multiple audiences:
Fabric is part of a larger Microsoft ecosystem. If your organization is already using other cloud subscription services, such as Azure, Microsoft 365, or Dynamics 365, then Fabric operates within the same Microsoft Entra tenant. Your organizational domain (for example, contoso.com) is associated with Microsoft Entra ID. Like all Microsoft cloud services, your Fabric tenant relies on your organization's Microsoft Entra ID for identity and access management.
Padoms
Many organizations have an on-premises Active Directory (AD) environment that they synchronize with Microsoft Entra ID in the cloud. This setup is known as a hybrid identity solution, which is out of scope for this article. The important concept to understand is that users, groups, and service principals must exist in Microsoft Entra ID for a cloud-based suite of services like Fabric to work. Having a hybrid identity solution will work for Fabric. We recommend talking to your Microsoft Entra administrators about the best solution for your organization.
For more information about the responsibilities of a Fabric administrator, see Tenant administration.
Most organizations have one Microsoft Entra tenant, so it's commonly true that a Microsoft Entra tenant represents an organization.
Usually, Microsoft Entra ID is set up before a Fabric implementation begins. However, sometimes it's when you provision a cloud service that you become aware of the importance of Microsoft Entra ID.
Padoms
Because most organizations have one Microsoft Entra tenant, it can be challenging to explore new features in an isolated way. You might qualify for a non-production developer tenant through the Microsoft 365 Developer Program; for details, see the FAQ. Alternatively, you can sign up for a 1-month free trial or purchase a Microsoft 365 plan.
A managed tenant has a global administrator assigned within Microsoft Entra ID. If a Microsoft Entra tenant doesn't exist for an organizational domain (for example, contoso.com), when the first user from that organization signs up for a Fabric trial or account, an unmanaged tenant is created in Microsoft Entra ID. An unmanaged tenant is also known as a shadow tenant, or a self-service-created tenant. It has a basic configuration, allowing the cloud service to work without assigning a global administrator.
To properly manage, configure, and support Fabric, a managed tenant is required. There's a process that a system administrator can follow to take over an unmanaged tenant so that they can manage it properly on behalf of the organization.
Padoms
The administration of Microsoft Entra ID is a broad and deep topic. We recommend that you assign specific people in your IT department as system administrators to securely manage Microsoft Entra ID for your organization.
Checklist - When reviewing your Microsoft Entra tenant for use with Fabric, key decisions and actions include:
You must consider how users will access your tenant when you have external users (such as customers, partners, or vendors) or when internal users must access another tenant outside of your organization. To access a different organizational tenant, a modified URL is used.
Every Microsoft Entra tenant has a globally unique identifier (GUID) known as the tenant ID. In Fabric, it's known as the customer tenant ID (CTID). The CTID is appended to the end of the tenant URL. You can find the CTID in the Fabric portal by opening the About Microsoft Fabric dialog window. It's available from the Help & Support (?) menu, which is located at the top-right of the Fabric portal.
Knowing your CTID is important for Microsoft Entra B2B scenarios. URLs that you provide to external users (for example, to view a Power BI report) must append the CTID parameter in order to access the correct tenant.
If you intend to collaborate with or provide content to external users, we recommend setting up custom branding. Use of a logo, cover image, and theme helps users identify which organizational tenant they're accessing.
Checklist - When granting external users permission to view your content, or when you have multiple tenants, key decisions and actions include:
Fabric administrators periodically need to work with the Microsoft Entra administrators.
The following list includes some common reasons for collaboration between Fabric administrators and Microsoft Entra administrators.
For more information, see Collaborate with other administrators.
Checklist - When considering how to work with your Microsoft Entra administrators, key decisions and actions include:
When a new tenant is created, resources are provisioned in Azure, which is Microsoft's cloud computing platform. Your geographic location becomes the home region for your tenant. The home region is also known as the default data region.
The home region is important because:
The home region for the organization's tenant is set to the location of the first user that signs up. If most of your users are located in a different region, that region might not be the best choice.
You can determine the home region for your tenant by opening the About Microsoft Fabric dialog window in the Fabric portal. The region is displayed next to the Your data is stored in label.
You might discover that your tenant resides in a region that isn't ideal. You can use the Multi-Geo feature by creating a capacity in a specific region (described in the next section), or, you can move it. To move your tenant to another region, your global Microsoft 365 administrator should open a support request.
The relocation of a tenant to another region isn't a fully automated process, and some downtime is involved. Be sure to take into consideration the prerequisites and actions that are required before and after the move.
Padoms
Because a lot of effort is involved, when you determine that a move is necessary, we recommend that you do it sooner rather than later.
Checklist - When considering the home region for storing data in your tenant, key decisions and actions include:
Some organizations have data residency requirements. Data residency requirements typically include regulatory or industry requirements for storing data in a specific geographic region. Data sovereignty requirements are similar, but more stringent because the data is subject to the laws of the country or region in which the data is stored. Some organizations also have data localization requirements, which dictate that data created within certain borders needs to remain within those borders.
Regulatory, industry, or legal requirements can require you to store certain data elsewhere from the home region (described in the previous section). In these situations, you can benefit from the Multi-Geo feature by creating a capacity in a specific region. In this case, you must assign workspaces to the correct capacity to ensure that the workspace data is stored in the desired geographic location.
Multi-Geo support enables organizations to:
Piezīme
The Multi-Geo feature is available with any type of capacity license (except shared capacity). It's not available with Premium Per User (PPU) because data stored in workspaces assigned to PPU is always stored in the home region (just like shared capacity).
Checklist - When considering other specific data regions for your tenant, key decisions and actions include:
For more considerations, actions, decision-making criteria, and recommendations to help you with Power BI implementation decisions, see Power BI implementation planning.
Padoms
To learn how to manage a Fabric tenant, we recommend that you work through the Administer Microsoft Fabric module.
Notikumi
Power BI DataViz pasaules čempionāts
14. febr. 16 - 31. marts 16
Ar 4 iespējām piedalīties, jūs varētu laimēt konferences paketi un iekļūt LIVE Grand Finale Lasvegasā
Uzzināt vairākApmācība
Mācību ceļš
Solution Architect: Design Microsoft Power Platform solutions - Training
Learn how a solution architect designs solutions.
Sertifikācija
Microsoft Certified: Identity and Access Administrator Associate - Certifications
Demonstrate the features of Microsoft Entra ID to modernize identity solutions, implement hybrid solutions, and implement identity governance.
Dokumentācija
Power BI implementation planning: Tenant administration - Power BI
This article introduces key considerations for administering a Fabric tenant.
Power BI implementation planning: Subscriptions, licenses, and trials - Power BI
This article helps you to plan for subscriptions, licenses, and trials for Power BI and Microsoft Fabric.
Power BI implementation planning: User tools and devices - Power BI
Learn about user tools and managing devices to enable and support Power BI consumers and authors in the organization.