Activate the new Power BI Embedded

Reports for Dynamics 365 for Finance and

Operations, Versions 7.2/7.3/8.0/8.1/10.0

Author: Helmut Wimmer helmut.wimmer@microsoft.com

Date: 20.12.2019
Version: 2.6

IMPORTANT:
These postings are provided "AS IS" with no warranties and confer no
rights. You assume all risk for your use.
Only use these postings in a demo environment.

1
Table of contents
README FIRST ......................................................................................................................................... 3
Introduction............................................................................................................................................. 4
Step 1: Create standard Power BI Connection (for Non-Analytical Workspaces) ................................... 4
Step 2: Create an Entity Store Database (AxDW) SQL Azure Database .................................................. 5
Step 3: Add a Power BI Embedded Workspace to your Azure subscription ......................................... 10
Step 4: Add Power BI users to your AxDW SQL Azure Database .......................................................... 23
Step 5: Tweak web.config file................................................................................................................ 26
Step 6: Create tables in the AxDW SQL Azure Database ....................................................................... 28
Step 7: Deploy the Power BI Embedded reports................................................................................... 28
Step 8: Modify the Power BI Embedded reports .................................................................................. 30
Final thoughts ........................................................................................................................................ 34
Appendix A: Overview of available Power BI Embedded Reports in Dynamics 365 ............................. 35
Accounts payable: Vendor payments................................................................................................ 35
Budgeting: Ledger budgets and forecast .......................................................................................... 39
Cash and bank management: Bank management............................................................................. 40
Cash and bank management: Cash overview – all companies.......................................................... 41
Cash and bank management: Cash overview – current company .................................................... 43
Credit and collections: Customer credit and collections................................................................... 45
Expense management: Expense overview ........................................................................................ 50
Fixed assets: Fixed asset management ............................................................................................. 52
Fleet management: Reservation management ................................................................................. 53
Fleet management: Details report .................................................................................................... 54
General ledger: CFO Overview .......................................................................................................... 56
Human resources: Personnel management ...................................................................................... 59
Human resources: Compensation management............................................................................... 65
Human resources: Benefits ............................................................................................................... 68
Human resources: Recruitment management .................................................................................. 70
Procurement and sourcing: Purchase and spend analysis ................................................................ 72
Production control: Production performance ................................................................................... 75
Project management and accounting: Project management ........................................................... 78
Sales and marketing: Sales and profitability performance ............................................................... 81
Warehouse management: Warehouse performance ....................................................................... 84
Talent: Employee Development ........................................................................................................ 86
Talent: Learning ................................................................................................................................. 89
Employee Development Operations ................................................................................................. 92

2
Appendix B: Changelog.......................................................................................................................... 97

README FIRST

As of Version 2.6 of this document (dated Dec 20th 2019) I wanted to make one very important note:

If you cannot deploy or use a Power BI Workspace collection in your Azure subscription, you might
need to do some additional steps (which I’m not aware of as I do not need them) to get this running.

From what I’ve heard and seen in the last couple of months, you might need to contact Azure
support to have your Azure subscription whitelisted to be able to use the Power BI Workspace
collections (which are retiring now) in your Azure subscription. This might or might not help or work,
but as I said, I do not need to do this as:

I am still deploying Power BI Workspace Collections in the same Azure subscription that I was using
when I wrote the first version of this document back in July 2017.

So, from my point of view (and my D365FO environments), if you have an Azure subscription where
you had deployed a Power BI Workspace Collection in the last couple of months, you should still be
able to create new collections in this subscription. This is possible for me in my subscription at the
time I am writing this, but as the Power BI Workspace collections are retiring, this may fail to work in
future.

Additional and existing thanks go to:

Angelos Angelides

Bas van Gameren

Boštjan Golob from partner Adacta

3
Introduction

Starting with the July 2017 Update (aka V7.2), a couple of Analytic Workspaces have been provided.
As Analytical Workspaces only work with Power BI Embedded Reports and they only work with a SQL
Azure Database, here are some steps on how to get it working.

NOTE: On July 29th 2017 a couple of blog posts have been published to get the Power BI Embedded
reports running:

https://blogs.msdn.microsoft.com/dynamicsaxbi/2017/07/29/accessing-analytical-workspaces-on-
1box-environment/

https://blogs.msdn.microsoft.com/dynamicsaxbi/2017/07/29/deploy-power-bi-embedded-service-
for-dynamics-365-for-operations/

https://blogs.msdn.microsoft.com/dynamicsaxbi/2017/07/29/deploy-azure-sql-server-for-hosting-
entity-store-database/

https://blogs.msdn.microsoft.com/dynamicsaxbi/2017/07/29/publish-the-entity-store-database-on-
azure-sql-server/

https://blogs.msdn.microsoft.com/dynamicsaxbi/2017/07/29/configuring-1box-to-enable-analytical-
workspaces-and-reports/

The steps outlined in the blog posts are very similar to this document.

Step 1: Create standard Power BI Connection (for Non-Analytical

Workspaces)

NB: This step is not necessary for getting the Power BI Embedded Workspaces. But if you want to use
the “old” workspaces showing Tiles/KPIs from Power BI, you can: Create the “standard” Power BI
connection from Operations as outlined here: https://docs.microsoft.com/en-
us/dynamics365/unified-operations/dev-itpro/analytics/configure-power-bi-integration#register-
your-finance-and-operations-deployment-as-a-web-app-in-the-azure-portal

4
Step 2: Create an Entity Store Database (AxDW) SQL Azure Database

Go to the Azure Portal https://portal.azure.com and create a new SQL Azure Database.

Some important entries:

Database Name AxDW

Subscription Assign your valid subscription
Resource Group Create a new Resource Group for your SQL Azure Database
Select Source Blank Database
Server Create a new server
Server Name Choose a valid name for your server, like myserverd365
You will need the server name later
Server admin login axdbadmin
Password Use the same password as in your cloud-hosted environment
created in LCSt
Location Choose a location of your choice (I used North Europe)
Pricing tier When deploying all measurements, the size of the database will
be approx. 5.5 GB, so you cannot choose the Basic tier. I chose
Standard with 50GB. You can also take more, seems to be the
same price for a given tier and DTU.
NOTE: If you do not choose a Premium tier, Clustered
Columnstore Indexes (CCI) will not be created in your SQL Azure
Database which may result in lower performance
NOTE (New in V2.3): if you choose at least a Pricing tier of
Standard S3 (=100 DTUs), Clustered Columnstore Indexes (CCI)
CAN be created (as of March 21st 2018), please see the Note at
the end of Step 2
NOTE (new in V2.6): you may want to explore other pricing
options for the SQL server, such as vCore based Serverless but
you may and will need additional/other steps for setting up your
logins as e.g. Serverless doesn’t give you direct access to the
master database.
Collation Use the standard collation provided:
SQL_Latin1_General_CP1_CI_AS

Next you’ll find some screenshots for creating the SQL Azure Database and SQL Azure Database
Server.

5
Dialog: Creation of new SQL Azure Database

6
Dialog: Creation of new SQL Azure Server (after clicking on “Server” on the previous screen)

7
NOTE on Additional Azure Security (New in V2.6):

On your SQL Azure Server (the Server, not the Database !), make sure you go to “Firewall and virtual
networks” and switch the toggle “Allow Azure services and resources to access this server” to ON.

8
NOTE on Columnstore Clustered Indexes (New in V2.3):

If you want to leverage Columnstore Clustered Indexes on the Entity Store Database, you must use
one of the following:

1. Premium Database (Min. Price approx.. USD 456 per month, depending on Azure Region)
2. PremiumRS Database (In Preview; Min. Price approx. USD 115 per month; depending on
Azure Region)
3. Standard Database S3/100 DTU (Min. Price USD 146 per month; depending on Azure region)

If you go for option 1 or 2 (Premium or PremiumRS), the columnstore clustered indexes will be
created automatically when you Hit “Refresh” on the Entity Store form.

If you go for option 3, the columnstore clustered indexes will NOT be created automatically on the
SQL Azure database, but there is a way you can get them:

(1) Do NOT change the web.config file to point to the SQL Azure database as outlined in Step 5.
Instead, leave it as it is.
(2) Refresh the Entity Store as outlined in Step 6 to the LOCAL AxDW database on your OneBox
machine.
(3) After all tables/views have been created, export the local AxDW database and import it into
a new SQL Azure Database (Minimum Size S3/100 DTU) as outlined here:
https://blogs.msdn.microsoft.com/dynamicsaxbi/2017/07/29/publish-the-entity-store-
database-on-azure-sql-server/
(4) After the database has been imported to SQL Azure, you can change the web.config file as
outlined in Step 5.
(5) You can continue with Step 7 and publish the Power BI Embedded reports.

Please be aware that if there are any changes to the data entities and you need to refresh them
again, you might lose your columnstore clustered indexes again.

Please be also aware that if you later on change the size of your SQL database to a tier below S3/100
DTU, the columnstore clustered indexes will STAY in the database but any query will give an error,
therefore the Power Bi Embedded reports will not work anymore.

And finally: if you don’t want to hassle around → you do NOT NEED the Columnstore Clustered
indexes in your SQL Azure Entity Store Database! The Power BI Embedded reports will work just fine
without them, just a little slower.

9
Step 3: Add a Power BI Embedded Workspace to your Azure
subscription

Big cheers to Boštjan Golob from partner Adacta for this.

NOTE (New in V2.3): Power BI Workspace collections will be deprecated in June 2018. How Power BI
Embedded will work in a Dynamics 365 for Finance and Operations OneBox environment afterwards
is yet unknown…

NOTE (New in V2.5): Power BI Workspace collections are deprecated now. You need to create them
via the Template deployment and obtain the Access Keys via PowerShell.

To create a new PBI Workspace collection click on the big + in the Azure Portal (New), search for
“Template deployment".

Click on Create:

10
Click on “Build your own template in the editor”

Paste the following in the template editor, make sure there are no extra line breaks when you paste
it in the editor in Azure portal:

"$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",

"contentVersion": "1.0.0.0",

"parameters": {},

"resources": [

"type": "Microsoft.PowerBI/workspaceCollections",

"sku": {

"name": "S1",

"tier": "Standard"

},

"name": "GIVE YOUR PBI WORKSPACE COLLECTION A NAME HERE!!!!",

"apiVersion": "2016-01-29",

"location": "North Europe"

11
You can, of course, choose a location other than North Europe. Click on Save to save the Template.

12
After saving the template, choose a Resource group or create a new one, choose the Azure location
of your Power BI Embedded Workspace and click on Purchase.

13
NOTE (new in V2.5): The way to obtain the access keys for the Power BI workspace collection has
changed. You cannot retrieve them anymore from the Azure Portal. You have to use PowerShell to
get them.

References:
https://docs.microsoft.com/en-us/powershell/azure/install-az-ps?view=azps-2.3.2

https://docs.microsoft.com/en-us/powershell/module/az.powerbiembedded/get-
azpowerbiworkspacecollectionaccesskey?view=azps-2.3.2

1. Start PowerShell (e.g. ISE) as an administrator:

NOTE (New in V2.6): If you run this from the D365FO VM, you might need to upgrade your
.NET version from https://dotnet.microsoft.com/download/dotnet-framework

2. Enter the following commands to install the Az module for PowerShell (and klick on “Yes” to
all prompts regarding policy changes, security, etc.):

set-executionpolicy remotesigned

Install-Module -Name Az -AllowClobber

Import-Module Az.PowerBIEmbedded

Connect-AzAccount

NOTE (New in V2.6): If your account is assigned to multiple Azure subsriptions, you might
end up being logged into the wrong tenant/subscription. To correct this you need to find the
workspace subscription ID within Azure portal, copy it and then use the following PowerShell
command Set-AzContext -SubscriptionId “<subscription id>”

3. Now you can get the 2 access keys by running the following command in PowerShell:

Get-AzPowerBIWorkspaceCollectionAccessKey -
ResourceGroupName "NAMEOFYOURRESOURCEGROUP" -
WorkspaceCollectionName "NAMEOFYOURWORKSPACECOLLECTION"

14
You will get a result like this with your access keys:

NOTE (new in V2.6): An easier way to obtain your keys is using Azure Cloud Shell.

You can start Azure Cloud Shell by going to https://shell.azure.com/ or by clicking the Cloud Shell

icon in the top line of the Azure Portal (next to the search bar). For the next examples and
screenshots, I will be using https://shell.azure.com/

First you need to select which Azure subscription you want to connect to:

15
Next, make sure you select PowerShell (and not Bash):

If you havent’t used Azure Cloud Shell on your Azure subscription before, you will see this
error/information message:

Click on “Create storage” and provide valid names for the Resource group, Storage account and File
share (no spaces allowed):

16
After creating the necessary storage, you will be welcomed by Azure Cloud Shell:

You can now get your Power BI Workspace collection keys by issuing the following commands in
Azure Cloud Shell.

1. Import-Module Az.PowerBIEmbedded

Connect-AzAccount

2. Now you can get the 2 access keys by running the following command in PowerShell:

Get-AzPowerBIWorkspaceCollectionAccessKey -
ResourceGroupName "NAMEOFYOURRESOURCEGROUP" -
WorkspaceCollectionName "NAMEOFYOURWORKSPACECOLLECTION"

17
You know what’s coming next: copy the 2 keys and use it later in the web.config file:

18
The following paragraphs and screenshots are kept for reference but are not applicable anymore.

After creation of the PBI workspace collection, open it, go to Access Keys and copy the 2 values for
KEY1 and KEY2, you will need them later.

NOTE (new in V2.1; changed screenshots and some wording in V2.4):

After you have successfully created the first workspace using the Template deployment, you can
create subsequent new Power BI Embedded Workspaces in the same Azure subscription (e.g. for
other demo environments) by clicking on the New (+) icon in the Azure Portal, and select Power BI
Workspace Collection (Note: Changed in V2.4, used to say “Power BI Embedded” which was never
the case).

19
Click in “Create” in the following screen:

20
In the next screen, scroll down (!!!). Here, you can click now on “Create a workspace collection” to
create a new PBI Workspace collection.

21
Now you can select a name, resource group and location for your new Power BI Embedded
Workspace collection:

After the workspace has been created, just copy the two Key values (as seen on page 11) and use
them in your next demo environment.

22
Step 4: Add Power BI users to your AxDW SQL Azure Database

VM into your demo environment. Open SQL Server Management studio and and connect to your SQL
Azure Database. As the name of your server, use the one you created in Step 1, something like
myserverd365.database.windows.net. User name = axdbadmin

Create a new Query, make sure you are in the master database and enter the following lines:

CREATE LOGIN axdwadmin WITH PASSWORD = 'samepasswordasinyourlcsenvironment';

CREATE LOGIN axdwruntimeuser WITH PASSWORD = 'samepasswordasinyourlcsenvironment';

Screenshot example:

23
Create another query, make sure you are in the AxDW database (you can choose the database with
Ctrl-U) and enter the following lines:

CREATE USER axdwadmin FROM LOGIN axdwadmin;

CREATE USER axdwruntimeuser FROM LOGIN axdwruntimeuser;

Screenshot example:

Create another query, make sure you are in the AxDW database and enter the following lines:

ALTER ROLE db_owner ADD MEMBER axdwadmin;

ALTER ROLE db_datareader ADD MEMBER axdwruntimeuser;

Screenshot example:

24
NOTE (New in V2.2): Troubleshooting tips/screenshots:

After you have created your logins and database users, your database should look like this:

Database logins:

Database users:

25
Step 5: Tweak web.config file

VM into your demo environment. Open Notepad with “Run as administrator”, otherwise you will not
be able to save the file.

In Notepad, open the following file: J:\AosService\WebRoot\web.config

(New in V2.3): Depending on your version (7.2/7.3/8.0), the file could also be placed in
K:\AosService\WebRoot\web.config

NOTE (new in V2.1):

Make sure you enter the correct values in the yellow highlighted text. It should be the values that
you have entered/copied in step 1 (Server name = your SQL Azure Server Name) and Step 3 (the 2
access keys for your Power BI Workspace collection and the name of your Power BI Workspace
collection).

First, search for the following line:

<add key="BiReporting.DWServer" value="should be the name of your windows server" />

Change the line to:

<add key="BiReporting.DWServer" value="nameofyoursqlazureserver.database.windows.net" />

Second, add the following lines at the end of the <add key> section, just before </appSettings>:

<add key="PowerBIEmbedded.AccessKey" value="thevalueyoucopied in Step3" />

<add key="PowerBIEmbedded.AccessKey2" value="thevalueyoucopied in Step 3" />

<add key="PowerBIEmbedded.ApiUrl" value="https://api.powerbi.com" />

<add key="PowerBIEmbedded.IsPowerBIEmbeddedEnabled" value="true" />

<add key="PowerBIEmbedded.WorkspaceCollectionName" value="the name of your PBI Workspace

collection" />

After the modifications, your web.config file should look something like this:

DWServer section:

26
End of <add key> section:

After you have saved the web.config file, Restart your IIS server on the VM. After restart, make sure
you still can open the D365 client. If not, you messed up something in the web.config file. But the
error message shown will point you to the line you have to change.

Restart the Batch Service (Microsoft Dynamics 365 Unified Operations: Batch Management Service)
in the Services console.

27
Step 6: Create tables in the AxDW SQL Azure Database

After restarting the IIS and Batch Service, open the Entity Store form in D365 and Refresh some of
the Aggregate Measurements. With that, the necessary tables will be created in the AxDW database
and filled with data. You can check if that worked by looking into your AxDW database in SQL
Management studio and check if tables have been created.

NOTE: Begin with just one measurement and check if the Power Bi Report shows up. If everything
looks okay, you can deploy the remaining measurements.

Step 7: Deploy the Power BI Embedded reports

Well, if all worked well until here, this is easy: just open an Analytical Workspace in the D365 client
(that uses PBI Embedded) and click on the “Analytics” tab. Wait a little, as D365 now figures out that
the PBI report has not yet been published to PBI and will do so. After that, you will see your Power BI
Embedded report in the D365 client. I have attached 2 screenshots here from my environment so I
hope you believe me

28
29
Step 8: Modify the Power BI Embedded reports

If you want to edit/modify the out-of-the-box Power BI Embedded reports, you can do so in Visual
Studio-

Note: Most of the reports will have the “Read-only” attribute set in the file system. Therefore, if you
want to save the modified report, you will have to unselect the Read-only attribute from Windows
File Explorer. Find the report name and file path in the “File path” line in Appendix A, right click on
the report, select “Properties”, unselect the Read-only attribute and click OK/Apply.

You can now either directly open the report from Windows File Explorer or you can use Visual Studio.

If you want to modify from Visual Studio, expand the “Resources” node:

Find the Power BI Embedded report you want to modify (names can be found using the “AOT
Resource” line in Appendix A, right click on the Resource and select “Open designer”.

30
Power BI Desktop will be opened (of course you need to install Power BI Desktop first if you haven’t
already done so).

Note: Power BI Desktop will not show any values as it knows nothing about your connection to the
Azure SQL database. If you want to see values while you are modifying/editing, you have to change
the Data Source Settings in Power BI Desktop as described here: https://docs.microsoft.com/en-
us/dynamics365/unified-operations/dev-itpro/analytics/power-bi-content-microsoft-
partners#download-and-extend-readymade-reports-that-are-distributed-via-lcs

After you have made your changes, save the report in Power BI Desktop.

As last step, you need the do a Build for the model(s) the report(s) are located in. The model name
can be retrieved e.g. from the file path where the report is stored in the filesystem.

Example: if the report you are modifying is

J:\AosService\PackagesLocalDirectory\ApplicationWorkspaces\ApplicationWorkspaces\AxResource\
ResourceContent\PowerBIReport\VendorPaymentAnalysisOverview.pbix, then you would need to do
a build for the model ApplicationWorkspaces.

Alternatively, you’ll find the name of the model next to the Resource name in the AOT in Visual
Studio.

31
Select the necessary model(s) and click on Build.

After the build is completed, open your Dynamics 365 Client and the modified report will be shown
(a Refresh in the browser might be necessary if you already had the Dynamics 365 client open).

Note: I did not have to “undeploy” the report; after the build was completed the modified report was
shown in the Dynamics 365 client. If you run into problems and want to undeploy one the reports
and publish it again to the Power BI Workspace collection in Azure, you can do as follows:

Open SQL Server Management Studio on your VM, go to the database AxDB, expand the tables node
and find the table dbo.PBIEMBEDDEDREPORTCONFIG. Right click the table and select “Edit Top 200
Rows”.

32
In the newly opened Query Editor Window, select the report you want to re-publish and delete it
(Right mouse → delete or just Press the Del key).

After the record has been deleted from the table, simply reopen the Workspace/Form in the
Dynamics 365 client and the report will be redeployed.

33
Final thoughts

The Entity Store DB usually makes use of Columnstore Clustered Indexes (CCI). If your SQL Azure
Database (created in Step 2) is not using a Premium pricing tier, those Indexes will not be created
resulting in lower query performance of your Analytical workspaces.

You may want to copy an already existing AxDW Entity Store database (locally stored on your OneBox
Demo environment) to a SQL Azure Database. Some guidance steps are provided here:
https://docs.microsoft.com/en-us/azure/sql-database/sql-database-import If you are not using a
Premium Pricing tier for your SQL Azure Database, you may need to delete the Columnstore
Clustered Indexes before exporting.

I did not have to give my user a Power BI Pro subscription.

34
Appendix A: Overview of available Power BI Embedded Reports in
Dynamics 365

The overview will be sectioned by module/main menu and always contain the menu path to the
report, the link to the documentation on docs.microsoft.com, the AOT resource name, the file path
of the pbix file, the used views and tables (if it’s a table it will show the suffix _MATERIALIZED) from
the entity store database and screenshots of all report pages.

Accounts payable: Vendor payments

Menu path: Accounts payable > Workspaces > Vendor payments

Docs https://docs.microsoft.com/en-us/dynamics365/unified-
operations/financials/accounts-payable/Vendor-payments-workspace
AOT resource VendPaymentBIReport
File path J:\AosService\PackagesLocalDirectory\ApplicationWorkspaces\ApplicationWo
rkspaces\AxResource\ResourceContent\PowerBIReport\VendorPaymentAnal
ysisOverview.pbix
Used VendPaymentBIMeasure_VendPaymentBIInvoicesDue
Views/Tables VendPaymentBIMeasure_VendTable
VendPaymentBIMeasure_VendPaymentBIInvoicesPaid
VendPaymentBIMeasure_VendPaymentBIVendorCustomerBalance
VendPaymentBIMeasure_VendPaymentBIPaymentsInWorkflow

35
36
37
38
Budgeting: Ledger budgets and forecast

Menu path: Budgeting > Workspaces > Ledger budgets and forecasts
Docs https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-
itpro/analytics/ledger-budgets-power-bi
AOT resource BudgetTrackingWorkspacePBIX
File path J:\AosService\PackagesLocalDirectory\ApplicationWorkspaces\ApplicationWo
rkspaces\AxResource\ResourceContent\PowerBIReport\Budget tracking
workspace.pbix
Used LedgerActivityMeasure_LedgerActivityMeasureGroup
Views/Tables BudgetActivityMeasure_BudgetActivityMeasureGroup
LedgerActivityMeasure_MainAccountLegalEntity
LedgerActivityMeasure_FiscalPeriodDateEntity_MATERIALIZED
LedgerActivityMeasure_Ledger
BudgetActivityMeasure_BudgetTransactionCode_MATERIALIZED
LedgerActivityMeasure_BICompanyView_MATERIALIZED

39
Cash and bank management: Bank management

Menu path: Cash and bank management > Workspaces > Bank management
Docs N/A
AOT resource BankBalanceWorkspacePBIX
File path J:\AosService\PackagesLocalDirectory\ApplicationWorkspaces\ApplicationWo
rkspaces\AxResource\ResourceContent\PowerBIReport\BankBalanceWorkspa
ce.pbix
Used LedgerCovLiquidityMeasurement_Date
Views/Tables LedgerCovLiquidityMeasurement_LedgerCovForecastActual
LedgerCovLiquidityMeasurement_LedgerCovBankAccountDimension

40
Cash and bank management: Cash overview – all companies

Menu path: Cash and bank management > Workspaces > Cash overview – all companies
Docs https://docs.microsoft.com/en-us/dynamics365/unified-
operations/financials/cash-bank-management/Cash-Overview-Power-BI-
content
AOT resource LedgerCovEnterprisePBIX
File path J:\AosService\PackagesLocalDirectory\ApplicationWorkspaces\ApplicationWo
rkspaces\AxResource\ResourceContent\PowerBIReport\CFPBICashOverviewE
nterprise.pbix
Used LedgerCovLiquidityMeasurement_Date
Views/Tables LedgerCovLiquidityMeasurement_LedgerCovLiquidity
LedgerCovLiquidityMeasurement_LedgerCovLiquidityInflowOutflowBalanceEn
terprise
LedgerCovLiquidityMeasurement_LedgerCovLiquidityTransactionCurrency
LedgerCovLiquidityMeasurement_LedgerCovForecastActual
LedgerCovLiquidityMeasurement_LedgerCovBankAccountDimension

41
42
Cash and bank management: Cash overview – current company

Menu path: Cash and bank management > Workspaces > Cash overview – current
company
Docs https://docs.microsoft.com/en-us/dynamics365/unified-
operations/financials/cash-bank-management/Cash-Overview-Power-BI-
content
AOT resource LedgerCovCompanyPBIX
File path J:\AosService\PackagesLocalDirectory\ApplicationWorkspaces\ApplicationWo
rkspaces\AxResource\ResourceContent\PowerBIReport\CFPBICashOverviewC
ompany.pbix
Used LedgerCovLiquidityMeasurement_Date
Views/Tables LedgerCovLiquidityMeasurement_LedgerCovLiquidity
LedgerCovLiquidityMeasurement_LedgerCovLiquidityTransactionCurrency
LedgerCovLiquidityMeasurement_LedgerCovForecastActual
LedgerCovLiquidityMeasurement_LedgerCovLiquidityInflowOutFlowBalanceC
ompany
LedgerCovLiquidityMeasurement_LedgerCovBankAccountDimension

43
44
Credit and collections: Customer credit and collections

If the user has access to the menu item “Cross company analytics” (AOT Menu item name:
CustCollectionsBICrossCompanyAnalytics) the report “Analytics – all companies” will be displayed.
Otherwise, the report “Analytics – current company” will be displayed.

Menu path: Credit and collections > Workspaces > Customer credit and collections
Docs https://docs.microsoft.com/en-us/dynamics365/unified-
operations/financials/accounts-receivable/credit-collections-power-bi
AOT resource CustCollectionsBIReportCrossCompany (→ all companies)
CustCollectionsBIReport (→ current company)
File path J:\AosService\PackagesLocalDirectory\ApplicationWorkspaces\ApplicationWo
rkspaces\AxResource\ResourceContent\PowerBIReport\Credit and collections
management cross company.pbix
J:\AosService\PackagesLocalDirectory\ApplicationWorkspaces\ApplicationWo
rkspaces\AxResource\ResourceContent\PowerBIReport\Credit and collections
management.pbix
Used CustCollectionsBIMeasurements_CustCollectionsBIActivitiesOpen
Views/Tables CustCollectionsBIMeasurements_CustTable
CustCollectionsBIMeasurements_CustCollectionsBIActivitiesAverageCloseTim
e
CustCollectionsBIMeasurements_CustCollectionsBICustOnHold
CustCollectionsBIMeasurements_CustCollectionsBISalesOnHold
CustCollectionsBIMeasurements_CustCollectionsBICollectionStatus
CustCollectionsBIMeasurements_CustCollectionsBIWriteOff
CustCollectionsBIMeasurements_CustCollectionsBICaseAverageCloseTime
CustCollectionsBIMeasurements_CustCollectionsBIInterestNotes
CustCollectionsBIMeasurements_CustCollectionsBICasesOpen
CustCollectionsBIMeasurements_CustCollectionsBIAgedBalances
CustCollectionsBIMeasurements_CustCollectionsBICollectionLetterAmounts
CustCollectionsBIMeasurements_CustCollectionsBIExpectedPayment
CustCollectionsBIMeasurements_CustCollectionsBICollectionLetter
CustCollectionsBIMeasurements_CustCollectionsBIBalancesDue
CustCollectionsBIMeasurements_CustCollectionsBIDSO30
CustCollectionsBIMeasurements_CustCollectionsBICredit

45
46
47
48
49
Expense management: Expense overview

Menu path: There is no menu entry for this report, but a menu item exists, therefore you
can only open the report by adding/changing the following to your URL:
https://<tenantname>.cloudax.dynamics.com/?cmp=usmf&mi=trvexpensead
minworkspaceembeddedreport
Docs N/A
AOT resource TrvExpenseAdminWorkspacePBIX
File path J:\AosService\PackagesLocalDirectory\ApplicationSuite\Foundation\AxResour
ce\ResourceContent\PowerBIReport\Expense Admin.pbix
Used TrvBIPersonalExpenseMeasure_TrvBIPersonalExpenseView
Views/Tables TrvBICashAdvanceMeasure_TrvBICashAdvanceMeasureGroup
TrvBIExpenseMeasure_Currency
TrvBIExpenseMeasure_Company
TrvBIExpenseMeasure_Worker
TrvBIExpenseMeasure_TrvBIExpenseMeasureGroup
TrvBIExpenseMeasure_Date
TrvBIExpenseWorkflowMeasure_TrvBIExpenseWorkflowView
TrvBICashAdvanceWorkflowMeasure_TrvBIExpenseWorkflowView
TrvBIRequisitionWorkflowMeasure_TrvBIExpenseWorkflowView
TrvBIRequisitionMeasure_TrvBIRequisitionView

50
51
Fixed assets: Fixed asset management

Menu path: Fixed assets > Workspaces > Fixed asset management
Docs https://docs.microsoft.com/en-us/dynamics365/unified-
operations/financials/fixed-assets/Fixed-asset-management-workspace
AOT resource FixedAssetsOverviewBIReport
File path J:\AosService\PackagesLocalDirectory\ApplicationWorkspaces\ApplicationWo
rkspaces\AxResource\ResourceContent\PowerBIReport\FixedAssetsOverview
.pbix
Used AssetTransactionMeasure_FixedAssets
Views/Tables AssetTransactionMeasure_AssetTransactionSummaryEntity
AssetTransactionMeasure_FixedAssetLocation

52
Fleet management: Reservation management

Menu path: Fleet management > Workspaces > Reservation management

Docs N/A
AOT resource FMPBIWorkspaces
File path J:\AosService\PackagesLocalDirectory\FleetManagement\FleetManagement\
AxResource\ResourceContent\PowerBIReport\FMPBIWorkspaces.pbix
Used FMAggregateMeasurements_ChargeType
Views/Tables FMAggregateMeasurements_FMCustomerProflie
FMAggregateMeasurements_FMRentalCharges
FMAggregateMeasurements_FMVehicle
FMAggregateMeasurements_RentalStartDate
FMAggregateMeasurements_StatusDate
FMAggregateMeasurements_TransationDate
FMAggregateMeasurements_VehicleInventory

53
Fleet management: Details report

This is a special Power BI Report that will be invoked if you click on one of the following areas in the
Fleet Reservation management report:

• TOTAL REVENUE by CHARGE TYPE

• TOTAL REVENUE by CUSTOMER

Menu path: Fleet management > Workspaces > Reservation management

Docs N/A
AOT resource FMPBIReports
File path J:\AosService\PackagesLocalDirectory\FleetManagement\FleetManagement\
AxResource\ResourceContent\PowerBIReport\FMPBIReports.pbix
Used FMAggregateMeasurements_ChargeType
Views/Tables FMAggregateMeasurements_FMCustomerProflie
FMAggregateMeasurements_FMRentalCharges
FMAggregateMeasurements_FMVehicle
FMAggregateMeasurements_RentalStartDate
FMAggregateMeasurements_StatusDate
FMAggregateMeasurements_TransationDate
FMAggregateMeasurements_VehicleInventory

54
55
General ledger: CFO Overview

Menu path: General ledger > Workspaces > CFO Overview

Docs https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-
itpro/analytics/CFO-power-bi
AOT resource LedgerCFOWorkspacePBIXt
File path J:\AosService\PackagesLocalDirectory\ApplicationWorkspaces\ApplicationWo
rkspaces\AxResource\ResourceContent\PowerBIReport\CFO Overview.pbix
Used BudgetActivityMeasure_BudgetActivityMeasureGroup
Views/Tables LedgerActivityMeasure_FiscalPeriodDateEntity_MATERIALIZED
LedgerActivityMeasure_Ledger
LedgerActivityMeasure_MainAccountEntity_MATERIALIZED
LedgerCovLiquidityMeasurement_LedgerCovForecastActual
LedgerCovLiquidityMeasurement_LedgerCovLiquidityInflowOutflowBalanceEn
terprise
BudgetActivityMeasure_BudgetTransactionCode_MATERIALIZED
PurchaseCube_ReleasedProducts
PurchaseCube_ProcurementCategory
PurchaseCube_Vendor
PurchaseCube_VendorInvoiceLines
CustCollectionsBIMeasurements_CustCollectionsBICredit
CustCollectionsBIMeasurements_CustCollectionsBIBalancesDue
SalesCube_Customer
CustCollectionsBIMeasurements_CustCollectionsBIAgedBalances
SalesCube_CustomerInvoiceLines
SalesCube_SalesCategory
SalesCube_ReleasedProducts
CustCollectionsBIMeasurements_CustTable
LedgerActivityMeasure_BICompanyView_MATERIALIZED
PurchaseCube_Date

56
57
58
Human resources: Personnel management

Note: there are 2 versions of this report, one for “all companies” and one for “current company”. I
haven’t found out which version will be displayed, might be security settings related.

Menu path: Human resources > Workspaces > Personnel management

Docs https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-
itpro/analytics/workforce-analysis-power-bi-content-pack
AOT resource HCMBIWorkforceAllCompanies
HCMBIWorkforce
File path J:\AosService\PackagesLocalDirectory\PersonnelManagement\PersonnelMan
agement\AxResource\ResourceContent\PowerBIReport\WorkforceAllCompa
nies.pbix
J:\AosService\PackagesLocalDirectory\PersonnelManagement\PersonnelMan
agement\AxResource\ResourceContent\PowerBIReport\WorkforceCurrentCo
mpany.pbix
Used Workforce_CurrentWorker
Views/Tables Workforce_TerminatedWorker
Workforce_WorkerTrend
Workforce_CurrentPosition
Workforce_PastPositionAssignment
Workforce_PositionTrend
Workforce_CalendarOffset
Workforce_Company
Workforce_Date
Workforce_Demographics
Workforce_Employment
Workforce_Job
Workforce_Position
Workforce_ReportsToWorkerName
Workforce_WorkerName
Workforce_WorkerTitle
Workforce_GeographicLocation
Workforce_MassHireLine
Workforce_MassHireProject

59
60
61
62
63
64
Human resources: Compensation management

Note: there are 2 versions of this report, one for “all companies” and one for “current company”. I
haven’t found out which version will be displayed, might be security settings related.

Menu path: Human resources > Workspaces > Compensation management

Docs https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-
itpro/analytics/compensation-power-bi
AOT resource HCMBICompensationAllCompanies
HCMBICompensation
File path J:\AosService\PackagesLocalDirectory\PersonnelManagement\PersonnelMan
agement\AxResource\ResourceContent\PowerBIReport\CompensationAllCo
mpanies.pbix
J:\AosService\PackagesLocalDirectory\PersonnelManagement\PersonnelMan
agement\AxResource\ResourceContent\PowerBIReport\CompensationCurren
tCompany.pbix
Used Workforce_CurrentWorker
Views/Tables Workforce_TerminatedWorker
Workforce_WorkerTrend
Workforce_CurrentPosition
Workforce_PastPositionAssignment
Workforce_PositionTrend
Workforce_CurrentCompensation
Workforce_CalendarOffset
Workforce_Company
Workforce_Compensation
Workforce_Date
Workforce_Demographics
Workforce_Employment
Workforce_Job
Workforce_Position
Workforce_ReportsToWorkerName
Workforce_WorkerBenefit
Workforce_WorkerName
Workforce_WorkerTitle
Workforce_Skill
Workforce_GeographicLocation

65
66
67
Human resources: Benefits

Note: there are 2 versions of this report, one for “all companies” and one for “current company”. I
haven’t found out which version will be displayed, might be security settings related.

Menu path: Human resources > Workspaces > Benefits

Docs https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-
itpro/analytics/benefits-power-bi
AOT resource HCMBIBenefitsAllCompanies
HCMBIBenefits
File path J:\AosService\PackagesLocalDirectory\PersonnelManagement\PersonnelMan
agement\AxResource\ResourceContent\PowerBIReport\BenefitsAllCompanie
s.pbix
J:\AosService\PackagesLocalDirectory\PersonnelManagement\PersonnelMan
agement\AxResource\ResourceContent\PowerBIReport\BenefitsCurrentCom
pany.pbix
Used Workforce_CurrentWorker
Views/Tables Workforce_TerminatedWorker
Workforce_WorkerTrend
Workforce_CurrentPosition
Workforce_PastPositionAssignment
Workforce_PositionTrend
Workforce_CurrentCompensation
Workforce_CalendarOffset
Workforce_Company
Workforce_Compensation
Workforce_Date
Workforce_Demographics
Workforce_Employment
Workforce_Job
Workforce_Position
Workforce_ReportsToWorkerName
Workforce_WorkerBenefit
Workforce_WorkerName
Workforce_WorkerTitle
Workforce_GeographicLocation

68
69
Human resources: Recruitment management

Note: there are 2 versions of this report, one for “all companies” and one for “current company”. I
haven’t found out which version will be displayed, might be security settings related.

Menu path: Human resources > Workspaces > Recruitment management

Docs https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-
itpro/analytics/recruiting-analysis-power-bi-content-pack
AOT resource HCMBIRecruitingAllCompanies
HCMBIRecruiting
File path J:\AosService\PackagesLocalDirectory\PersonnelManagement\PersonnelMan
agement\AxResource\ResourceContent\PowerBIReport\RecruitingAllCompan
ies.pbix
J:\AosService\PackagesLocalDirectory\PersonnelManagement\PersonnelMan
agement\AxResource\ResourceContent\PowerBIReport\RecruitingCurrentCo
mpany.pbix
Used Recruiting_CalendarOffset
Views/Tables Recruiting_Company
Recruiting_Date
Recruiting_Demographics
Recruiting_Employment
Recruiting_GeographicLocation
Recruiting_Job
Recruiting_Performance
Recruiting_ApplicantName
Recruiting_EmployedApplicant
Recruiting_Applicant
Recruiting_TerminatedApplicant
Recruiting_Media
Recruiting_RecruitmentProject

70
71
Procurement and sourcing: Purchase and spend analysis

Menu path: Procurement and sourcing > Inquiries and reports > Purchase performance
analysis > Purchase and spend analysis
Docs https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-
itpro/analytics/purchase-content-pack-for-power-bi
AOT resource PurchaseSpendAnalysisPowerBIContentPack
File path J:\AosService\PackagesLocalDirectory\ApplicationSuite\Foundation\AxResour
ce\ResourceContent\PowerBIReport\Purchase spend analysis.pbix
Used PurchaseCube_Company
Views/Tables PurchaseCube_Date
PurchaseCube_ProcurementCategory
PurchaseCube_VendorInvoiceLines
PurchaseCube_ReleasedProducts
PurchaseCube_Vendor

72
73
74
Production control: Production performance

Menu path: Production control > Inquiries and reports > Production performance analysis
> Production performance
Docs https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-
itpro/analytics/production-performance-power-bi
AOT resource ProductionPerformancePowerBIContentPack
File path J:\AosService\PackagesLocalDirectory\ApplicationSuite\Foundation\AxResour
ce\ResourceContent\PowerBIReport\Production performance.pbix
Used ProductionCube_RouteTransactions
Views/Tables ProductionCube_ReleasedProducts
ProductionCube_ProductionOrder
ProductionCube_ReportedAsFinished
ProductionCube_Resources
ProductionCube_Company
ProductionCube_RequirementDate
ProductionCube_PlannedProductionOrder
ProductionCube_RouteTransactionDate
ProductionCube_CostCalculationCompare
ProductionCube_InventSite
ProductionCube_Ended

75
76
77
Project management and accounting: Project management

Menu path: Project management and accounting > Workspaces > Project management
Docs https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-
itpro/analytics/practice-manager-power-bi
AOT resource ProjPracticeManagerPBIX
File path J:\AosService\PackagesLocalDirectory\ApplicationSuite\Foundation\AxResour
ce\ResourceContent\PowerBIReport\PracticeManager.pbix
Used ProjectAccountingCube_ProjectTransactionDate
Views/Tables ProjectAccountingCube_Company
ProjectAccountingCube_Actuals
ProjectAccountingCube_Forecasts
ProjectAccountingCube_ProjectPlannedCostsView
ProjectAccountingCube_ActualHourUtilization
ProjectAccountingCube_Customer
ProjectAccountingCube_Projects
ProjectAccountingCube_ForecastModels
ProjectAccountingCube_ProjectCategory
ProjectAccountingCube_TotalEstimatedCosts
ProjectAccountingCube_Resource
ProjectAccountingCube_ResourceCategory

78
79
80
Sales and marketing: Sales and profitability performance

Menu path: Sales and marketing > Inquiries and reports > Sales performance analysis >
Sales and profitability performance
Docs https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-
itpro/analytics/sales-profitability-performance-content-pack
AOT resource SalesProfitabilityPerformancePowerBIContentPack
File path J:\AosService\PackagesLocalDirectory\ApplicationSuite\Foundation\AxResour
ce\ResourceContent\PowerBIReport\Sales and profitability performance.pbix
Used SalesCube_Company
Views/Tables SalesCube_Customer
SalesCube_CustomerInvoiceLines
SalesCube_DueDate
SalesCube_SalesCategory
SalesCube_ReleasedProducts

81
82
83
Warehouse management: Warehouse performance

Menu path: Warehouse management > Inquiries and reports > Warehouseperformance
analysis > Warehouse performance
Docs https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-
itpro/analytics/warehouse-power-bi-content
AOT resource WHSWarehousePowerBIContentPack
File path J:\AosService\PackagesLocalDirectory\ApplicationSuite\Foundation\AxResour
ce\ResourceContent\PowerBIReport\Warehouse performance.pbix
Used WHSWarehouse_Company
Views/Tables WHSWarehouse_CustPackingSlipOnTimeStatus
WHSWarehouse_Customer
WHSWarehouse_DeliveryDate
WHSWarehouse_ReleasedProducts
WHSWarehouse_SalesLines
WHSWarehouse_Vendor
WHSWarehouse_Warehouses
WHSWarehouse_WorkCreateDateTime
WHSWarehouse_WorkLines
WHSWarehouse_WorkClosedDateTime
WHSWarehouse_CycleCountingWarehouseWorkLines
WHSWarehouse_PurchaseLines

84
85
Talent: Employee Development

This Power BI Embedded report is only available in the Dynamics 365 for Talent app, although the
pbix file and the AxResource are available in the standard Dynamics 365 for Finance and Operations
app, but there is no menu item or form available (You may of course create your own form and menu
item using the resource).

Menu path: D365 Talent > Employee Development

Docs https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-
itpro/analytics/employee-development-PBI
AOT resource HCMBIEmployeeDevelopment
File path J:\AosService\PackagesLocalDirectory\PersonnelManagement\PersonnelMan
agement\AxResource\ResourceContent\PowerBIReport\EmployeeDevelopme
ntAllCompanies.pbix
J:\AosService\PackagesLocalDirectory\PersonnelManagement\PersonnelMan
agement\AxResource\ResourceContent\PowerBIReport\EmployeeDevelopme
ntCurrentCompany.pbix
Used Workforce_CurrentWorker
Views/Tables Workforce_TerminatedWorker
Workforce_WorkerTrend
Workforce_CurrentPosition
Workforce_PastPositionAssignment
Workforce_PositionTrend
Workforce_PersonSkill
Workforce_JobPreferredSkill
Workforce_CalendarOffset
Workforce_Company
Workforce_Date
Workforce_Demographics
Workforce_Employment
Workforce_Job
Workforce_Position
Workforce_ReportsToWorkerName
Workforce_WorkerName
Workforce_WorkerTitle
Workforce_Skill
Workforce_GeographicLocation

86
87
88
Talent: Learning

This Power BI Embedded report is only available in the Dynamics 365 for Talent app, although the
pbix file and the AxResource are available in the standard Dynamics 365 for Finance and Operations
app, but there is no menu item or form available (You may of course create your own form and menu
item using the resource).

Menu path: D365 Talent > Learning

Docs https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-
itpro/analytics/learning-power-bi
AOT resource HCMBITraining
File path J:\AosService\PackagesLocalDirectory\PersonnelManagement\PersonnelMan
agement\AxResource\ResourceContent\PowerBIReport\LearningAllCompanie
s.pbix
J:\AosService\PackagesLocalDirectory\PersonnelManagement\PersonnelMan
agement\AxResource\ResourceContent\PowerBIReport\LearningCurrentCom
pany.pbix
Used Training_CalendarOffset
Views/Tables Training_Company
Training_Course
Training_CourseAgenda
Training_CourseAttendees
Training_CourseSkill
Training_Date
Training_Demographics
Training_Demographics
Training_Job
Training_Position
Training_WorkerName
Training_WorkerTitle
Training_Instructor
Training_Instructor

89
90
91
Employee Development Operations

This Power BI Embedded report is not available neither in the Dynamics 365 for Talent app nor the
standard Dynamics 365 for Finance and Operations app. Only the pbix file and the AxResource are
available, but there is no menu item or form available (You may of course create your own form and
menu item using the resource).

The reports shows 2 additional tabs/pages and the first page is slightly different to the report in the
Talent app.

Menu path: N/A

Docs https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-
itpro/analytics/employee-development-PBI
AOT resource HCMBIEmployeeDevelopmentOperations
File path J:\AosService\PackagesLocalDirectory\PersonnelManagement\PersonnelMan
agement\AxResource\ResourceContent\PowerBIReport\EmployeeDevelopme
ntOperationsAllCompanies.pbix
J:\AosService\PackagesLocalDirectory\PersonnelManagement\PersonnelMan
agement\AxResource\ResourceContent\PowerBIReport\EmployeeDevelopme
ntOperationsCurrentCompany.pbix
Used Workforce_CurrentWorker
Views/Tables Workforce_TerminatedWorker
Workforce_WorkerTrend
Workforce_CurrentPosition
Workforce_PastPositionAssignment
Workforce_PositionTrend
Workforce_PersonSkill
Workforce_JobPreferredSkill
Workforce_CalendarOffset
Workforce_Company
Workforce_Date
Workforce_Demographics
Workforce_Employment
Workforce_Job
Workforce_Performance
Workforce_Position
Workforce_ReportsToWorkerName
Workforce_WorkerName
Workforce_WorkerTitle
Workforce_Skill
Workforce_GeographicLocation

92
NOTE: The screenshots are taken from Power BI Desktop as there is no form available in Dynamics
365

93
94
95
96
Appendix B: Changelog
V1.01: Added restart Batch Service in Step 5

V1.02: Change SQL Azure Database size from 100MB to 2GB in Step 2

V1.03: Added Template deployment script for creating a PBI Workspace in Step 3

V1.04: Changed Pricing tier for SQL Azure Database in Step 2

V2.00: Streamlining, adding some screenshots, removed GitHub section in Step 3, added Final
Thoughts section

V2.1: Changed font size of the deployment script in Step 3, as it might put an additional unnecessary
line break when you copy it into the Azure Portal
Added alternative way of creating a PBI workspace collection after the Template Deployment script
has been run at least once (Step 3)

Added screenshots for web.config file (Step 5)

Added Note in Step 6

Added Note with blog posts in Introduction

Added Appendix A with all available PBI Embedded reports

Moved Changelog to Appendix B

V2.2: Add color highlighting for the text to be entered/changed and a note regarding this in Step 5

Added one color highlighting and a troubleshooting/screenshot section in Step 4

Added Step 8: Modify the Power BI Embedded reports

V2.3: Validated for Version 8.0

Step 2: Changed value for “Server admin login” from axlocaladmin to axdbadmin (as axlocaladmin is
not available anymore and replaced by a “Builtin\admin….” account); also changed screenshot on
page 6

Step 2: Added note that Columnstore Clustered indexes will be used if the database is at least Size S3
(100 DTU)

Step 2: Added Note on Columnstore Clustered Indexes at the end of Step 2

Step 3: Added Note about depreciation of Power BI Workspace collections in June 2018

Step 5: Added alternative location for web.config file (for e.g. V8.0 versions)

V2.4: Validated for Version 8.1

Step 3: Exchanged the screenshots

V2.5: Validated for Version 10.0.4 PU28

Step 3: Added section for getting the access keys via PowerShell

97
V2.6: Validate for Version 10.0.7 PU31

Added README FIRST

Step 2: Added setting for Additional Azure security (“Allow Azure services and resources to access
this server”)

Step 2: Added note on Pricing tier for Azure SQL Server

Step 3: Added note on setting the context to a subscription ID if the account is assigned to multiple
Azure subscriptions

Step 3: Added note to obtain keys via Azure Cloud Shell

98