Microsoft Fabric adoption roadmap: User support

Straipsnis
11/14/2023

Note

This article forms part of the Microsoft Fabric adoption roadmap series of articles. For an overview of the series, see Microsoft Fabric adoption roadmap.

This article addresses user support. It focuses primarily on the resolution of issues.

The first sections of this article focus on user support aspects you have control over internally within your organization. The final topics focus on external resources that are available.

For a description of related topics, including skills mentoring, training, documentation, and co-development assistance provided to the internal Fabric user community, see the Mentoring and user enablement article. The effectiveness of those activities can significantly reduce the volume of formal user support requests and increase user experience overall.

Types of user support

If a user has an issue, do they know what their options are to resolve it?

The following diagram shows some common types of user support that organizations employ successfully:

Diagram shows the four types of internal Fabric user support, and the two types of external support, which are described in the table below.

The six types of user support shown in the above diagram include:

Type	Description
	Intra-team support (internal) is very informal. Support occurs when team members learn from each other during the natural course of their job.
	Internal community support (internal) can be organized informally, formally, or both. It occurs when colleagues interact with each other via internal community channels.
	Help desk support (internal) handles formal support issues and requests.
	Extended support (internal) involves handling complex issues escalated by the help desk.
	Microsoft support (external) includes support for licensed users and Fabric administrators. It also includes comprehensive documentation.
	Community support (external) includes the worldwide community of experts, Microsoft Most Valued Professionals (MVPs), and enthusiasts who participate in forums and publish content.

In some organizations, intra-team and internal community support are most relevant for self-service data and business intelligence (BI)—content is owned and managed by creators and owners in decentralized business units. Conversely, the help desk and extended support are reserved for technical issues and enterprise data and BI (content is owned and managed by a centralized BI team or Center of Excellence). In some organizations, all four types of support could be relevant for any type of content.

Tip

For more information about business-led self-service, managed self-service, and enterprise data and BI concepts, see the Content ownership and management article.

Each of the six types of user support introduced above are described in further detail in this article.

Intra-team support

Intra-team support refers to when team members learn from and help each other during their daily work. Self-service content creators who emerge as your champions tend to take on this type of informal support role voluntarily because they have an intrinsic desire to help. Although it's an informal support mode, it shouldn't be undervalued. Some estimates indicate that a large percentage of learning at work is peer learning, which is particularly helpful for analysts who are creating domain-specific analytics solutions.

Note

Intra-team support does not work well for individuals who are the only data analyst within a department. It's also not effective for those who don't have very many connections yet in their organization. When there aren't any close colleagues to depend on, other types of support, as described in this article, become more important.

Internal community support

Assistance from your fellow community members often takes the form of messages in a discussion channel, or a forum set up specifically for the community of practice. For example, someone posts a message that they're having problems getting a DAX calculation to work or are looking for the right Python module to import. They then receive a response from someone in the organization with suggestions or links.

Tip

The goal of an internal Fabric community is to be self-sustaining, which can lead to reduced formal support demands and costs. It can also facilitate managed self-service content creation occurring on a broader scale versus a purely centralized approach. However, there will always be a need to monitor, manage, and nurture the internal community. Here are two specific tips:

Be sure to cultivate multiple experts in the more difficult topics like T-SQL, Python, Data Analysis eXpressions (DAX) and the Power Query M formula language. When a community member becomes a recognized expert, they could become overburdened with too many requests for help.
A greater number of community members might readily answer certain types of questions (for example, report visualizations), whereas a smaller number of members will answer others (for example, complex T-SQL or DAX). It's important for the COE to allow the community a chance to respond yet also be willing to promptly handle unanswered questions. If users repeatedly ask questions and don't receive an answer, it will significantly hinder growth of the community. In this case, a user is likely to leave and never return if they don't receive any responses to their questions.

An internal community discussion channel is commonly set up as a Teams channel or a Yammer group. The technology chosen should reflect where users already work, so that the activities occur within their natural workflow.

One benefit of an internal discussion channel is that responses can come from people that the original requester has never met before. In larger organizations, a community of practice brings people together based on a common interest. It can offer diverse perspectives for getting help and learning in general.

Use of an internal community discussion channel allows the Center of Excellence (COE) to monitor the kind of questions people are asking. It's one way the COE can understand the issues users are experiencing (commonly related to content creation, but it could also be related to consuming content).

Monitoring the discussion channel can also reveal additional analytics experts and potential champions who were previously unknown to the COE.

Important

It's a best practice to continually identify emerging champions, and to engage with them to make sure they're equipped to support their colleagues. As described in the Community of practice article, the COE should actively monitor the discussion channel to see who is being helpful. The COE should deliberately encourage and support community members. When appropriate, invite them into the champions network.

Another key benefit of a discussion channel is that it's searchable, which allows other people to discover the information. It is, however, a change of habit for people to ask questions in an open forum rather than private messages or email. Be sensitive to the fact that some individuals aren't comfortable asking questions in such a public way. It openly acknowledges what they don't know, which might be embarrassing. This reluctance might reduce over time by promoting a friendly, encouraging, and helpful discussion channel.

Tip

You might be tempted to create a bot to handle some of the most common, straightforward questions from the community. A bot can work for uncomplicated questions such as "How do I request a license?" or "How do I request a workspace?" Before taking this approach, consider if there are enough routine and predictable questions that would make the user experience better rather than worse. Often, a well-created FAQ (frequently asked questions) works better, and it's faster to develop and easier to maintain.

Help desk support

The help desk is usually operated as a shared service, staffed by the IT department. Users who will likely rely on a more formal support channel include those who are:

Less experienced users.
Newer to the organization.
Reluctant to post a message to the internal discussion community.
Lacking connections and colleagues within the organization.

There are also certain technical issues that can't be fully resolved without IT involvement, like software installation and upgrade requests when machines are IT-managed.

Busy help desk personnel are usually dedicated to supporting multiple technologies. For this reason, the easiest types of issues to support are those which have a clear resolution and can be documented in a knowledgebase. For instance, software installation prerequisites or requirements to get a license.

Some organizations ask the help desk to handle only very simple break-fix issues. Other organizations have the help desk get involved with anything that is repeatable, like new workspace requests, managing gateway data sources, or requesting a new capacity.

Important

Your Fabric governance decisions will directly impact the volume of help desk requests. For example, if you choose to limit workspace creation permissions in the tenant settings, it will result in users submitting help desk tickets. While it's a legitimate decision to make, you must be prepared to satisfy the request very quickly. Respond to this type of request within 1-4 hours, if possible. If you delay too long, users will use what they already have or find a way to work around your requirements. That might not be the ideal scenario. Promptness is critical for certain help desk requests. Consider that automation by using Power Apps and Power Automate can help make some processes more efficient. For more information, see Tenant-level workspace planning.

Over time, troubleshooting and problem resolution skills become more effective as help desk personnel expand their knowledgebase and experience with supporting Fabric. The best help desk personnel are those who have a good grasp of what users need to accomplish.

Tip

Purely technical issues, for example data refresh failure or the need to add a new user to a gateway data source, usually involve straightforward responses associated with a service-level agreement (SLA). For instance, there could be an SLA to respond to blocking issues within one hour and resolve them within eight hours. It's generally more difficult to define SLAs for troubleshooting issues, like data discrepancies.

Extended support

Since the COE has deep insight into how Fabric is used throughout the organization, they're a great option for extended support should a complex issue arise. Involving the COE in the support process should be by an escalation path.

Managing requests as purely an escalation path from the help desk gets difficult to enforce since COE members are often well-known to business users. To encourage the habit of going through the proper channels, COE members should redirect users to submit a help desk ticket. It will also improve the data quality for analyzing help desk requests.

Microsoft support

In addition to the internal user support approaches discussed in this article, there are valuable external support options directly available to users and Fabric administrators that shouldn't be overlooked.

Microsoft documentation

Check the Fabric support website for high-priority issues that broadly affect all customers. Global Microsoft 365 administrators have access to additional support issue details within the Microsoft 365 portal.

Refer to the comprehensive Fabric documentation. It's an authoritative resource that can aid troubleshooting and search for information. You can prioritize results from the documentation site. For example, enter a site-targeted search request into your web search engine, like power bi gateway site:learn.microsoft.com.

Power BI Pro and Premium Per User end-user support

Licensed users are eligible to log a support ticket with Microsoft.

Tip

Make it clear to your internal user community whether you prefer technical issues to be reported to the internal help desk. If your help desk is equipped to handle the workload, having a centralized internal area collect user issues can provide a superior user experience versus every user trying to resolve issues on their own. Having visibility and analyzing support issues is also helpful for the COE.

Administrator support

There are several support options available for Fabric administrators.

For customers who have a Microsoft Unified Support contract, consider granting help desk and COE members access to the Microsoft Services Hub. One advantage of the Microsoft Services Hub is that your help desk and COE members can be set up to submit and view support requests.

Worldwide community support

In addition to the internal user support approaches described in this article, and Microsoft support options described previously, you can leverage the worldwide Fabric community.

The worldwide community is useful when a question can be easily understood by someone without domain knowledge, and when it doesn't involve confidential data or sensitive internal processes.

Publicly available community forums

There are several public community forums where users can post issues and receive responses from any user in the world. Getting answers from anyone, anywhere, can be very powerful and exceedingly helpful. However, as is the case with any public forum, it's important to validate the advice and information posted on the forum. The advice posted on the internet might not be suitable for your situation.

Publicly available discussion areas

It's very common to see people posting Fabric technical questions on social media platforms. You might find discussions, post announcements, and users helping each other.

Community documentation

The Fabric global community is vibrant. Every day, there are a great number of Fabric blog posts, articles, webinars, and videos published. When relying on community information for troubleshooting, watch out for:

How recent the information is. Try to verify when it was published or last updated.
Whether the situation and context of the solution found online truly fits your circumstance.
The credibility of the information being presented. Rely on reputable blogs and sites.

Considerations and key actions

Checklist - Considerations and key actions you can take for user support follow.

Improve your intra-team support:

Provide recognition and encouragement: Provide incentives to your champions as described in the Community of practice article.
Reward efforts: Recognize and praise meaningful grassroots efforts when you see them happening.
Create formal roles: If informal intra-team efforts aren't adequate, consider formalizing the roles you want to enact in this area. Include the expected contributions and responsibilities in the HR job description, when appropriate.

Improve your internal community support:

Continually encourage questions: Encourage users to ask questions in the designated community discussion channel. As the habit builds over time, it will become normalized to use that as the first option. Over time, it will evolve to become more self-supporting.
Actively monitor the discussion area: Ensure that the appropriate COE members actively monitor this discussion channel. They can step in if a question remains unanswered, improve upon answers, or make corrections when appropriate. They can also post links to additional information to raise awareness of existing resources. Although the goal of the community is to become self-supporting, it still requires dedicated resources to monitor and nurture it.
Communicate options available: Make sure your user population knows the internal community support area exists. It could include the prominent display of links. You can include a link in regular communications to your user community. You can also customize the help menu links in the Fabric portal to direct users to your internal resources.
Set up automation: Ensure that all licensed users automatically have access to the community discussion channel. It's possible to automate license setup by using group-based licensing.

Improve your internal help desk support:

Determine help desk responsibilities: Decide what the initial scope of Fabric support topics that the help desk will handle.
Assess the readiness level: Determine whether your help desk is prepared to handle Fabric support. Identify whether there are readiness gaps to be addressed.
Arrange for additional training: Conduct knowledge transfer sessions or training sessions to prepare the help desk staff.
Update the help desk knowledgebase: Include known questions and answers in a searchable knowledgebase. Ensure someone is responsible for regular updates to the knowledgebase to reflect new and enhanced features over time.
Set up a ticket tracking system: Ensure a good system is in place to track requests submitted to the help desk.
Decide whether anyone will be on-call for any issues related to Fabric: If appropriate, ensure the expectations for 24/7 support are clear.
Determine what SLAs will exist: When a specific service level agreement (SLA) exists, ensure that expectations for response and resolution are clearly documented and communicated.
Be prepared to act quickly: Be prepared to address specific common issues extremely quickly. Slow support response will result in users finding workarounds.

Improve your internal COE extended support:

Determine how escalated support will work: Decide what the escalation path will be for requests the help desk cannot directly handle. Ensure that the COE (or equivalent personnel) is prepared to step in when needed. Clearly define where help desk responsibilities end, and where COE extended support responsibilities begin.
Encourage collaboration between COE and system administrators: Ensure that COE members and Fabric administrators have a direct escalation path to reach global administrators for Microsoft 365 and Azure. It's critical to have a communication channel when a widespread issue arises that's beyond the scope of Fabric.
Create a feedback loop from the COE back to the help desk: When the COE learns of new information, the IT knowledgebase should be updated. The goal is for the primary help desk personnel to continually become better equipped at handling more issues in the future.
Create a feedback loop from the help desk to the COE: When support personnel observe redundancies or inefficiencies, they can communicate that information to the COE, who might choose to improve the knowledgebase or get involved (particularly if it relates to governance or security).

Questions to ask

Use questions like those found below to assess user support.

Who is responsible for supporting enterprise data and BI solutions? What about self-service solutions?
How are the business impact and urgency of issues identified to effectively detect and prioritize critical issues?
Is there a clear process for business users to report issues with data and BI solutions? How does this differ between enterprise and self-service solutions? What are the escalation paths?
What types of issues do content creators and consumers typically experience? For example, do they experience data quality issues, performance issues, access issues, and others?
Are any issues closed without them being resolved? Are there "known issues" in data items or reports today?
Is a process in place for data asset owners to escalate issues with self-service BI solutions to central teams like the COE?
How frequent are issues in the data and existing solutions? What proportion of these issues are found before they impact business end users?
How long does it typically take to resolve issues? Is this timing sufficient for business users?
What are examples of recent issues and the concrete impact on the business?
Do enterprise teams and content creators know how to report Fabric issues to Microsoft? Can enterprise teams effectively leverage community resources to unblock critical issues?

Caution

When assessing user support and describing risks or issues, be careful to use neutral language that doesn't place blame on individuals or teams. Ensure everyone's perspective is fairly represented in an assessment. Focus on objective facts to accurately understand and describe the context.

Maturity levels

The following maturity levels will help you assess the current state of your Power BI user support.

Level	State of user support
100: Initial	• Individual business units find effective ways of supporting each other. However, the tactics and practices are siloed and not consistently applied. • An internal discussion channel is available. However, it's not monitored closely. Therefore, the user experience is inconsistent.
200: Repeatable	• The COE actively encourages intra-team support and growth of the champions network. • The internal discussion channel gains traction. It's become known as the default place for questions and discussions. • The help desk handles a small number of the most common technical support issues.
300: Defined	• The internal discussion channel is popular and largely self-sustaining. The COE actively monitors and manages the discussion channel to ensure that all questions are answered quickly and correctly. • A help desk tracking system is in place to monitor support frequency, response topics, and priorities. • The COE provides appropriate extended support when required.
400: Capable	• The help desk is fully trained and prepared to handle a broader number of known and expected technical support issues. • SLAs are in place to define help desk support expectations, including extended support. The expectations are documented and communicated so they're clear to everyone involved.
500: Efficient	• Bidirectional feedback loops exist between the help desk and the COE. • Key performance indicators measure satisfaction and support methods. • Automation is in place to allow the help desk to react faster and reduce errors (for example, use of APIs and scripts).