Microsoft has jumped into the free, self-service data analysis space with Power BI.
Power BI offers basic data wrangling capabilities similar to Excel's Power Query. It also lets you create interactive visualizations, reports and dashboards with a few clicks or drag-and-drops; type natural-language questions about your data on a dashboard; and handle files that are too large for Excel.
It can work with dozens of data types -- not only Excel, Access and CSV files, but also Salesforce, Google Analytics, MailChimp, GitHub, QuickBooks Online and dozens of others. And, it will run R scripts -- meaning that any data you can pull in and massage via R you can import into Power BI.
A guide to Power BI
In this article, I've put together a step-by-step guide to starting with Power BI, along with a number of other resources to help you along:
- Data files
- Power BI Desktop vs. cloud service
- Personal vs. Enterprise gateways
- 12 important Power BI visualization concepts
- Data cleaning via scripts
What is Power BI exactly?
Power BI includes both a downloadable desktop program and a cloud service, each of which offers different but overlapping capabilities. Data wrangling is desktop-only; visualizations and reports can be created in either; dashboards and report sharing are cloud-only. In addition, there are mobile apps for iOS, Android and Windows that let you view your Power BI or SQL Server Reporting Services (SSRS) reports and dashboards.
At least for now, you can take advantage of most Power BI capabilities without paying -- although Microsoft is clearly betting that you'll like the basic cloud service enough to spring for a $9.99/month paid account. Chief benefits of the paid account are increased data storage (10GB vs. 1GB), more timely automated data refreshes, the ability to create enterprise "content packs" and higher streaming capacity.
Be advised, though, that Microsoft wants a business email address when you sign up for Power BI cloud service -- while it can't screen out all non-commercial addresses, it won't accept known free consumer addresses like Gmail.com. Accounts from .gov and .mil addresses aren't supported for direct sign-up at powerbi.com either, although addresses at .edu and .org are.
And if you'd like to use any of Power BI's free mobile apps, you'll need a Power BI cloud account or access to your organization's SQL Server.
On the other hand, Power BI Desktop (at least for now) is not only free but doesn't require an account, an email address or a credit card -- just a Windows PC.
If you'd like to learn how to use this new, still-evolving tool to create reports and dashboards, read on.
Importing data into Power BI
Power BI Desktop is the better place to begin, unless you're sure that your data is already in the format you need for visualization. (Which may be the case if, like me, you prefer to do your data wrangling with a scripting language like R or Python.)
If you're used to Excel, you might think that selecting File > Open is the way to start analyzing your data in Power BI. But you'd be wrong -- File > Open is only for an already existing Power BI project.
Instead, to import new data, click the Get Data button on the Home tab, choose your data source type and click Connect.
This will bring up a familiar Windows file-selection dialog. Choose your file and you'll see a preview of your data. If it looks okay and there's nothing more you want to do to the data before starting to graph and chart, hit Load. Otherwise, click Edit, which brings up the Power BI Query Editor.
In this article, I'm going to use monthly files of airline flight-delay information from last summer that I downloaded from the Federal Aviation Administration (FAA) website. I know -- especially where airlines are concerned, past performance is no guarantee of future results. But if you're going to book a flight this summer, it might be fun (if not necessarily predictive) to answer questions such as: Which airlines had the best and worst delays last summer? Are there any specific flights that do especially poorly or well? These Power BI charts can help you easily answer these questions.
If you want to follow along, you can download your own data files from the Department of Transportation website. Or if you want, you can download the same files I'm using here -- the file download is available to all members of the Computerworld Insider program; registration is free, so if you're not already an Insider, it's easy enough to sign up. Files include data for domestic flights in the U.S. by month (so if you want to check flights to Paris, this won't help). There are separate files for June, July, August and September.
Start by loading in the June file (2015_06_ONTIME.csv): Go to Get Data > CSV in Power BI. Select and open your file, and you'll see a preview of your data. Then click Edit (not Load) to bring up the Query Editor. Now we can do some data wrangling.
One thing that can be useful to check at this point is whether number columns are loading in as numeric (aligned to the right) or text (aligned to the left). In other words, if you see numbers that are flush left in your data preview, they're not importing correctly -- which is one reason to choose Edit and bring up the Query Editor window even if you don't think you need to make changes in your data's structure.
Once in the Query Editor, you can right-click on a column header and select "Change Type" in order to manually select a data type such as whole number, decimal number, date, date/time, etc. But there's plenty more we can do with this data besides checking column types.
Note: If you're not interested in data wrangling and want to get started with charts and graphs, load the summer15delays.csv file instead and skip ahead to the Easy visualizations section -- but do make sure that the flight number is changed from numeric to text when you import the file.
[Continues on next page]
Query Editor lets you reshape and transform data by, for example, merging multiple data sources and pivoting or unpivoting data. It can also handle common data drudgery like adding, deleting, renaming and moving columns.
For the flight-delay data, you want to combine multiple months into a single table, so don't start changing data within June until you've added July, August and September. Otherwise, you'd have to repeat the same transformations on each file before combining them.
To import more CSV files into this active Query Editor window, click on New Source > CSV and choose a file (you can select only one at a time), give the data preview a quick look and click OK.
Each data source should now be listed under Queries in the left panel. Next, in the Queries panel, click on the table that you want to add data to (for this example, you can choose 2015_06_ONTIME and add other months to that).
Click Append Queries (if your browser window is narrow, Append Queries may be under a Combine button), click on Three or more tables (the default is two tables) and follow the instructions in the dialog box.
Your 2015_06_ONTIME file should now have four months of data, not just June, so it's probably worth renaming it to something like 2015_SUMMER_ONTIME. You can right-click on it in the left-side Queries panel to rename it; or, with that query active (clicked on from the Queries panel), look at the Query Settings on the right panel and change text in the Name box under PROPERTIES.
Next, let's try merging two tables using a common column -- what's often called a join in SQL or using a lookup table in Excel.
The CARRIER column in 2015_06_ONTIME uses airline codes (such as AA) instead of airline names. It would be nice to have the complete airline names available since not all codes are intuitive -- AA may be obvious, but VX and B6 less so. I created a file of airline codes and carrier names, airlinecodes.csv, that's also available in the Computerworld Insider data download. You can import the file into the current Query Editor window using the New Source button.
On my system, airlinecodes.csv imported into Power BI without the correct column names. Instead, the columns were named "Column1" and "Column2" (obviously the system defaults) while the real column names, "Code" and "Airline," showed up as the first row of data. If that happens to you as well, look to the right on the Home ribbon and you should see an option to Use First Row As Headers. Click on that to fix it.
Next, let's add airline name information to the flight-delay data. With your main data source 2015_SUMMER_ONTIME active, select Merge Queries. In the dialog box that pops up, choose the query table with lookup information, in this case airlinecodes, and then click on the column header for the common column in each table: CARRIER in 2015_SUMMER_ONTIME and Code in the airlinecodes table.
Finally, choose what kind of merge/join you want -- they're described in the drop-down list. For example, the one we want, "Left Outer," means "Keep all rows from the first table whether or not there's a match in the second table." Power BI will now attempt to estimate how many matching rows there are, which is helpful if you've made a mistake and end up with zero matches and thus need to re-examine which columns you're using for the join and whether the data is formatted the same in both.
Everything good? Click OK and the join is done.
After the merge, you'll see a column on the far right of your data table labeled NewColumn, with a table icon to the left of the column name and arrows to the right. Click the arrows to expand that table column to view the data -- you can choose the columns you want to add to the original table.
If you want to move that Airline column closer to Carrier, head to the Transform tab. There you'll have the choice to move the new (or any other) column. In this case, using the Power BI interface, you can select the new column and then use the Move > To Beginning and then Move > Right four times in order to get the Airline column next to the Carrier column. But there's a less cumbersome way.
First, if you don't see a formula bar above your table, go to the View ribbon and check Formula Bar so it's visible. Then head to the Transform ribbon, make sure the Airline column is selected, and choose Move > To Beginning. You'll now see a formula in the M language that reorders the columns. Click Move > Right and you'll see how the formula changes. It looks like you could just cut and paste the Airline column where you want it to go -- but you can't make changes here.
Instead, go to View > Advanced Editor and you'll see all your steps as a script. Edit the Table.ReorderColumns line to put Airline when you want it, and click Done. Your Airline column should have moved.
There are a number of other operations available on the Transform menu as well, such as grouping values by one or more columns, splitting columns based on a separator or specific number of characters, and pivoting (similar to creating Excel pivot tables) or unpivoting (moving multiple columns of data into two columns: variable data, such as "Month" and value data, such as "June").
You can also do some basic statistical exploration using options on the Transform ribbon, such as counting rows or creating summary stats like count, average, median and standard deviation. When you perform a data summary, a table with the new summarized values will appear in place of your original data table. To get the view of your original data back, go to the Applied Steps column to the right of your data table and delete the summarizing function.
In fact, you can use Applied Steps to delete any step you've taken here, not just the most recent, which is rather handy. Unfortunately, there's not also an Undo after deleting a step in the Query Editor, so you can't bring something back that you've erased.
Select the Count Rows menu option on the Transform ribbon to see the number of rows; if you're using flight-delay files downloaded from Computerworld, you'll see there are slightly over two million rows -- more than you could pull into Excel and its limit of 1,048,576 rows. Delete the Count Rows step to return to the full data.
Right now there are over 50 columns in the summer flight-delay table. To make things more manageable, select just a few that you might want to use in some data visualizations: MONTH, FL_DATE, Airline, FL_NUM, ORIGIN, ORIGIN_CITY_NAME, DEST, DEST_CITY_NAME, CRS_DEP_TIME, DEP_DELAY, ARR_DELAY, CANCELLED, CARRIER_DELAY, WEATHER_DELAY, NAS_DELAY, SECURITY_DELAY, LATE_AIRCRAFT_DELAY.
Click the Choose Columns button on the Home ribbon, deselect Select All Columns and then check the boxes next to the columns you want to keep and click OK.
If you later decide you want to add back any column, you can return to the Query Editor by clicking Edit Queries and then click the settings gear next to Removed Other Columns in the Applied Steps column. That brings the dialog box back up with your prior selections, and you can add more columns to your project.
Finally, make sure to change columns that don't make sense as numbers into text. For example, unless you want Power BI to calculate sums of your flight numbers -- and you don't -- turn them into text. Otherwise, attempting to make graphs with these fields as categories won't work, and you'll end up wasting a fair amount of time (don't ask me how I know). You can convert FL_NUM and MONTH into text by right-clicking the column header and choosing Change Type > Text. Another tweak: The CANCELLED column shows 0 for false and 1 for true -- if you want, you can change that type to True/False.
Now comes the fun part.
Close out of the Query Editor with Close & Apply to get back to the main Power BI application. (Because these files are so large, this may take a little while.) At this point you might also want to do a File > Save to save your work as a Power BI project so that if something happens, you won't need to re-create your steps.
Your Power BI blank canvas should look something like this:
It would be nice to get rid of all the other query files that we merged into 2015_SUMMER_ONTIME, since we won't be using them again. If you go to the Fields panel on the right and try to right-click and choose Delete, you'll get a warning that you can't delete those queries because they're referenced by another query. However, you can right-click and then Hide them to get them out of the way.
Do that for all the queries except 2015_SUMMER_ONTIME. Now that there's only one query table left, the 2015_SUMMER_ONTIME table will automatically expand to show its column names. (When there are multiple queries in the menu, the column names don't appear by default; click the triangle next to one to expand it; right-click and choose Expand all to see all the queries' fields.)
Want to graph departure delays? Click the check box next to DEP_DELAY. You'll get a bar graph with one bar summing all the delay time in your data. (Power BI tries to guess what visualization will work best with your data if you don't specify.) Click Airline, and the graph will morph into a bar graph of each airline's total flight delays.
A sum of total delays by airline isn't that useful, though; the more flights an airline has, the more minutes delayed it's likely to have. But if you look under the Visualizations panel and find DEP_DELAY under Value, you can click the triangle drop-down menu and change the Sum of DEP_DELAY minutes to Average (or Median, if you prefer).
(If the graph is too small, just click and drag a corner of the box to resize it.)
The graph is currently sorted by airline alphabetically. If you want it sorted from highest to lowest, click the ellipsis at the top right and choose Sort By > Average of DEP_DELAY.
Arrival delays would be interesting, too. Drag ARR_DELAY onto the Value area of the panel and change it from Sum to Average. Click the ellipsis again at top right to sort by ARR_DELAY descending (if it defaults to ascending, just click again). You should now have a graph that looks like this:
(You can see a version of your graph that takes up the whole canvas by clicking on the "Focus mode" icon next to the ellipsis at the top right of the graph's borders.)
The default title is a little lame. You can change the title and a lot of design defaults by clicking the brush icon just below the Visualizations options. To edit a specific graph, make sure you click it so it's active (the bounding box is visible). Click on Title and you'll see options to change the title text, font color, size, alignment and so on.
There are also options to add data labels to the bars, change the X- and Y-axes, and more.
For example, you can change the title to Average Departure & Arrival Delays in Minutes, Jun - Sep 2015, bump up the text size and center-align. If you want to rename fields, you can do that on the Fields panel -- right-click a field and choose rename. Try changing DEP_DELAY to Dep Delay and ARR_DELAY to Arr Delay.
Well, it sure looks like Spirit Airlines wasn't the best choice last summer -- but maybe the airline has big delays in some airports but not others? We can revise the visualization to include just a few airports.
There are a couple of ways to narrow in on a subset of data. Filters can apply to one graph, the entire page or all pages in a multi-page report. You can change filters while editing a report; but if you subsequently share your work as a Power BI dashboard, read-only users will see only what you filtered and won't be able to add data back in.
Another choice is to add an interactive slicer. With slicers, if you later share your work with others, they can interactively filter data and add it back in.
Let's try both.
[Continues on next page]
Filtering your data
When I started working with Power BI in March, a major drawback was that you couldn't add a text search box to a report, table or slicer. If you were analyzing information with a lot different categories, such as U.S. flight data, it was pretty annoying to have to scroll through hundreds of cities on a list in order, say, to find St. Louis.
As of the June 30 Power BI Desktop software update, you can add a text-searchable slicer to your reports, making it easier to hone in on one item amidst hundreds (or thousands). More on that in a bit. But it's also possible that you know there are only a few items of interest among the hundreds in your list, and you'd like to create a report with just a subset of the data.
One way to do this is to filter a report down to a few key categories -- in this case, perhaps showing only some cities that are of known interest, such as where your company has offices.
To do this, click on an empty area of the canvas and then drag DEST_CITY_NAME onto the Report level filters (where you see the "Drag data fields here" area). Pick a few cities. If you're following along, I chose Atlanta, Boston, Chicago, Cleveland, Las Vegas, Los Angeles, New Orleans, New York, Philadelphia, San Francisco, San Jose, Seattle and Washington, D.C.
Click the DEST_CITY_NAME header on the filter to close it. Then do the same for ORIGIN_CITY_NAME -- drag it on top of the DEST_CITY_NAME filter and select the cities you want -- and you'll just have info for flights between your key cities.
At this point, it may be worth noting on the report itself that the data is now only for a few cities. You can add text to the page by clicking on the Text Box button on the Home ribbon. Move and shape it the way you want on the canvas and then write some text explaining which cities the report covers.
We can now make it easy for users to pick origin and destination cities by adding a couple of slicers. Click onto an empty area of the canvas, then click on the slicer visualization icon (it looks like a little filter/funnel on a table icon under Visualizations -- in the May 2016 version of Power BI, it's the third from last icon under Visualizations). Check ORIGIN_CITY_NAME. Now click on an empty area of the canvas again, click on the slicer icon a second time, and then click on DEST_CITY_NAME. Size and move slicers around the canvas as you like.
If you still have enough cities in your slicer that adding a search box is worthwhile, click the ellipsis in the top right of the slicer and select Search. That will add a text search box to the slicer.
If the text is a little small and hard to read, click on each slicer, then click the brush icon and choose a new text size under Items. Just as with the graph, you can change the title and click on the fields to rename them (from, say, ORIGIN_CITY_NAME to Origin City and DEST_CITY_NAME to Desintation City) and increase the Header font size.
You can probably now see the benefit of filtering the data first: Without that page-level filter, there would be more than 300 cities to scroll through on each slicer.
Finally, it might be interesting to see the actual flights, not just the airline. Drag Airline to an empty spot on the canvas and then add FL_NUM. You'll get a table. Add Dep Delay and Arr Delay, and then once again make sure to change both from Sum to Average (under Values). Rename FL_NUM to Flight. You can add the scheduled departure time by clicking on CRS_DEP_TIME and adding that to the table, too.
Now when you click on an origin and destination city in the slicers, you'll see all available flights and their average arrival and departure delays. If you click on one airline's bar in the graph, the table will show just that airline's flights.
(Note: It's not very easy to find, but you can customize how the graphics on your page interact with each other. Click on one graphic to activate it; then on the Format ribbon, choose Edit Interactions. The other graphics on the page will all have some additional icons: A filter and a circle with slash through it. Clicking on the filter means that graphic will change based on what happens in the active graphic; clicking the circle with slash means it will not.)
It's also easy to take the same graphics and decide to look at medians instead of averages, since a few unlucky very late flights could have an outsized effect on overall averages. As in Excel, you can add a page to your Power BI report by clicking the plus sign next to the tab with the page name (default should be Page 1).
Even handier, since we've got slicers and a graph all set up: Right-click on the page and duplicate it. It's now pretty easy to click on the graph; under the Value section, click on Average of Dep Delay and Average of Arr Delay and change each to Median. If you're following along, you'll also want to change the title of the graph and the table with flight data from Average to Median.
Every airline had a 0 or below median arrival delay for all these cities combined -- except for Spirit. When I just look at flights arriving in Boston, Spirit's delays look even more pronounced -- although to be fair, they might have just had a bad summer in 2015 and improved since then.
Interested in how average delays break down by month? Power BI has automatic drilldown by date fields, which we can see by creating a new visualization on a new page.
Again, right-click on Page 1 and duplicate it, click on the graph to activate it, then unclick Airlines and click on FL_DATE. You'll only see two bars on the chart, one each for arrival and departure.
That's because Power BI defaults to graphing by year, and we've only got one year's worth of data. Under Axis, you can click the x next to Year to delete that so the graph will stop aggregating annually (which is somewhat useless for this data). It now defaults to Quarter. That, too, isn't much use for this particular four-month data set, but let's pretend it is.
To enable Power BI's date drilldown, click the down arrow at the top right of the graph. Now, if you click one of the third-quarter bars, it will drill down to show you months. Click a month's bar, and it will zoom in on days for that month.
To go back up to larger time groups, click the up arrow at the top left of the graph. Note that while you're drilling up and down, you'll no longer be affecting other visuals on the page, so data on the table won't change.
The date drilldowns are automated for date fields, but you can set up drilldowns for any hierarchy. Activate the graph on the first page, then drag FL_NUM onto the Axis field, making sure it ends up below Airline. Nothing will appear to change on the graph except that drilldown icons appear.
Click on the down arrow at the top right to activate drilldown, click on an airline's bar, and you'll see all the data for that airline's individual flights. Again, because drilldown is active, you won't see any changes on the table. If you want to be able to manually filter the table for a specific airline while this is going on, you can either temporarily add Airline as a page-level filter or add a third slicer for Airline.
Click the up arrow at the top left to get back to the original graph, click the down arrow again to deactivate drilldown capabilities if it's still selected, and the graphic will work as it did before.
If you want to change the headline for the graph on this page, make the graph active once again, click the brush icon on the Visualizations panel and then click on Title.
For a final step, you may want to rename the page tabs from "Page 1" and "Duplicate of Page 1" to something more meaningful. This doesn't currently work the same way as in Excel -- instead of right-clicking a tab, you need to double-click on the tab name.
There are a lot more visualizations you can generate within Power BI. In addition to all the icons in the Visualizations panel, including tree maps and actual geographic maps, there are other graphics available for import from the Custom Visuals Gallery. If you find one you like, download it from the gallery and then import it using the ellipsis next to the last icon in the Visualizations panel. You've got to import it separately into any report where you want to use it. (You can find an example of one of the more recent custom visuals created by Microsoft Research here.)
There are a lot of other ways to visualize this data, such as looking at the columns with reasons for delays, but for now I'll move on.
[Continues on next page]
Sharing your work
After you've done some exploratory visualizations, you might want to share some of your analyses with co-workers. To do this, you first need to publish your data and report to the Power BI cloud service. Save your work, then go to Home > Publish. You'll need to sign into your Power BI account if you're not currently logged in (or create one if you don't yet have one).
After data is published to the Power BI cloud service, you'll be offered the chance to "Get Quick Insights" from your data. This is Microsoft's automated look through various data points in order to highlight things like outliers and correlations. Unfortunately, Quick Insights doesn't know that it shouldn't add together all the delay times -- it needs to average them to be meaningful. (I expect the default would work a lot better for files of data like sales and profits, where sums by region or store over time could make sense.)
I tried out Quick Insights by duplicating my project (I did a Save As to another name), and then grouping data by destination city, airline and flight. (If you want to follow along, go to Edit Queries > Transform > Group By and follow the dialog box to create a new column of average arrival delays, select Close & Apply, re-do your visualizations, then publish).
To get Quick Insights on a data set within the Power BI cloud service, click on the ellipsis next to its name in the left-hand menu (click the three-line menu icon at the top left to show the menu if it's not visible) and choose Quick Insights. (Can't find Quick Insights? Make sure you're doing this under Datasets and not under Reports.)
After looking at Quick Insights, go the main Power BI cloud page, sign in if you need to, click the three-horizontal-line icon at the top left to view the menu (if necessary), and you should see all your Datasets, Reports and Dashboards. If you already created visualization report pages in the desktop software before publishing to the service, they'll show up under Reports (your data, not surprisingly, shows up under Datasets).
You can share a report directly to the web for public viewing, which then also allows you to embed it somewhere on your own website: Go to File > Publish to Web. Be advised that although this was free while in beta, I haven't seen Microsoft guarantee that it will stay free since it moved out of preview in early July.
If this is private data you want to share with just a few other people, you'll need to share your work as a dashboard instead. If you'd like to share an entire report page as a dashboard, click the pin (thumbtack) icon just above the page and choose to add it to a new dashboard. You can also mix and match visualizations from different pages -- or even different data sets -- onto a dashboard by clicking on an individual visualization and then clicking on the pin icon at the top right of that visualization and pinning it to an existing or new dashboard. You can then click the share icon at the top right and share with others by entering their email addresses.
The dialog box is pretty self-explanatory, letting you decide whether recipients can re-share or just view. (As of this writing, row-level security is available for some data sets, allowing only certain users to see more sensitive information in a data set, but some of the features are in preview and are likely to change.)
You can embed web content, images, text boxes and videos into a dashboard from the dashboard itself; you can also create additional visualizations in a report and pin them to a dashboard, including adding "cards" that call out one or a couple of key metrics. You can edit your report in Power BI service by clicking the Edit Report link above the page and then pinning a new visualization to any dashboard.
You can allow your users to ask natural-language questions by clicking the setting gear icon on the top (black) nav bar, clicking Dashboards and then the specific dashboard you want to edit. Click the checkbox next to "Show the Q&A search box on this dashboard."
This feature lets you (or your dashboard viewers) generate new visualizations from a data set by typing in questions. Once I figured out appropriate formats for my queries, I found this a pretty compelling interface. For example, I imported data for monthly search visits to IDG's U.S. websites and then was able to view various slices of the data by typing in things like "Show me search visits by month for Computerworld" or "What month has the largest search visits for CIO". And while I could have created the same interactivity with slicers on a report page that I pinned to a dashboard, the value-add here is that users can ask questions that I didn't necessarily think to model for them.
For the flight data, I queried my dashboard with questions such as "What origin city has the largest average security delay?" (Adak Island Alaska. Who knew?) and "What destination city has the largest average weather delay from Boston?"
As you type in something that Power BI recognizes as possibly coming from your data set, the word is underlined and you see choices for what to select. Do you want Boston in Origin City or Destination City? Click and pick. If visualization type -- such as column or bar -- isn't the one you want, you can specify one in your query.
One quibble: Trying to pull data for a city like San Francisco or New York didn't work for me because the system didn't start recognizing the city name until I typed the fourth letter; three letters and a space didn't work so well. Fortunately, I could also use SFO (for San Francisco) or JFK and LGA (for New York) from the Origin airport code -- but that's something to keep in mind if you want to use this feature and have cities in your data.
If your data doesn't have intuitive column names, you can add a "synonym" to a data model -- in Desktop only -- for alternate ways to refer to a column. Click on the Relationships icon in the left panel (it's the third icon showing three boxes), select the Modeling ribbon, and you should see a Synonyms icon and list of fields to the right. If you click in the text box under Origin City, for example, you can enter additional substitute names such as Leaving.
In just a few weeks of working with Power BI, I found it to be a fairly intuitive platform for loading in data and quickly doing basic data exploration and visualization.
As of the Microsoft Data Insights Summit in March, Power BI was missing some functionality I consider basic -- text searching for slicers, conditional formatting for tables, calendar data-pickers as slicers -- but Microsoft has made progress since then on improving the platform. Conditional formatting for tables was added in the May 31 desktop update, searchable slicers arrived in the June 30 update and Microsoft says better date-range pickers are in the works.
The platform is being updated fairly frequently -- once a month for the Desktop, more often for the cloud service -- offering the promise of continued new features and functionality. And as an R user, I'm intrigued by the integration of R scripts within the software and Microsoft's recent announcement R graphics in the Power BI service (Pro account needed) -- although you definitely don't need to know or use R for Power BI.
If you already use Excel -- especially on Windows -- or are otherwise a Microsoft shop with corporate data stored in Microsoft infrastructure, I'd recommend downloading Power BI, signing up for a free account and taking Power BI for a test drive. If you don't use other Microsoft products, it may still be worthwhile to try the platform if you want to do some quick data exploration and analysis and don't currently have a favorite platform, since Power BI will pull in a lot of other data formats besides spreadsheets, SQL Server and Microsoft Azure.
While I was somewhat underwhelmed with the two online Content Pack data connections I tried (Adobe Analytics and Google Analytics), largely because they didn't cover long-term site content trends, that's not to say some of the others like Salesforce or MailChimp wouldn't work for you. And Microsoft is developing what it calls enterprise-class "solution templates" -- there are a couple of offerings for Salesforce and Dynamics CRM, for example -- that are aimed to make it easier to gear up corporate analytics reporting. (Microsoft says that Content Pack publishers are typically responsible for what scenarios to focus on.)
Bottom line? Microsoft designed Power BI for business users to do self-service analysis, in some cases with the help of IT to set up gateways or internal "Content Packs" connecting to internal data. It's not as robust a platform as, say, Tableau -- but it also doesn't carry Tableau's robust price tag for private data analysis. (Tableau Public is free but has less functionality than the paid software and isn't designed for sharing private data, which is usually critical for enterprise users.)
If you are a full-time data analyst or commercial designer creating publication-quality graphics, this may not be for you. But if you don't need high-end customization and functionality while analyzing data and sharing your work, this could be an attractive alternative.