Integrating Energy BI with AzureDevOps (Git), half 1: Cloud Integration



Energy BI is a strong software for creating and sharing interactive knowledge visualizations. However how will you collaborate with different builders in your Energy BI tasks and guarantee high quality and consistency throughout your experiences? On this collection of weblog posts, I’ll present you how one can combine Energy BI with Azure DevOps, a cloud-based software program improvement and supply platform. We will combine Azure DevOps with Energy BI Service (Material) in addition to Energy BI Desktop.
The present submit explains how one can arrange Azure DevOps and join a Energy BI Workspace.
The subsequent weblog submit will clarify how one can apply it to your native machine to combine your Energy BI Desktop tasks with Azure DevOps.

Earlier than we dive into the main points of Energy BI and Azure DevOps integration, let’s take a second to grasp what supply management techniques are and why they’re important for any software program challenge.

Supply management techniques, also referred to as model management techniques or revision management techniques, are instruments that assist builders handle the adjustments made to their code over time. They permit builders to trace, examine, and roll again adjustments when vital and collaborate with different builders on the identical challenge.

There are two primary kinds of supply management techniques: centralised and distributed. Centralised supply management techniques use Shopper-server strategy to retailer all of the code and its historical past in a single server, and builders want to connect with that server to entry or modify the code. Examples of centralised supply management techniques are Microsoft’s Group Basis Server (TFS) which rebranded to Azure DevOps Server in 2018, IBM’s ClearCase, and Apache’s Subversion.

Alternatively, distributed supply management techniques use a peer-to-peer strategy, permitting every developer to have an area copy of all the code repository, together with its historical past. Builders can work offline and sync their adjustments with different builders by way of a distant server. Examples of distributed supply management techniques are Git Software program and Mercurial, which takes us to the subsequent part. Let’s see what Git is.

Git is without doubt one of the world’s hottest and broadly used distributed supply management techniques. It was created by Linus Torvalds, the creator of Linux, in 2005. Git has many benefits over centralised supply management techniques, comparable to:

  • Velocity: Git is quick and environment friendly, performing most operations regionally with out community entry.
  • Scalability: Git can simply deal with giant and complicated tasks, because it doesn’t depend upon a single server.
  • Flexibility: Git helps numerous workflows and branching methods, permitting builders to decide on how they need to organise their code and collaborate with others.
  • Safety: Git makes use of cryptographic hashes to make sure the integrity and authenticity of the code.
  • Open-source: Git is free and open-source, which means anybody can use it, modify it, or contribute to it.

Whereas Git is fairly good, it has some disadvantages in contrast with a centralised supply management system. Listed below are some:

  • Complexity: Git has a steep studying curve, particularly for customers who’re new to distributed model management techniques. Understanding ideas comparable to branching, merging, rebasing, and resolving conflicts will be difficult for novices and typically even seasoned Git customers.
  • Collaboration challenges: Whereas distributed model management techniques like Git allow simple collaboration, they will additionally result in collaboration points. A number of builders engaged on the identical department concurrently could encounter conflicts that have to be resolved, which may introduce complexities and require additional effort.
  • Efficiency with giant repositories: Whereas Git performs fairly effectively on most operations, it will probably get abortive when working with giant repositories containing many information or a protracted historical past of commits. Operations comparable to cloning or trying out giant repositories will be time-consuming.

Azure DevOps is Microsoft’s cloud-based platform offering a set of instruments and providers for software program improvement. It encompasses a spread of capabilities for managing, planning, growing, testing, and delivering software program functions. Azure DevOps affords:

  • Azure Boards: A software for planning, monitoring, and managing work gadgets, comparable to consumer tales, duties, bugs, and so forth.
  • Azure Repos: A software for internet hosting Git repositories on-line, which is the primary focus of this weblog submit.
  • Azure Pipelines: A software for automating builds, exams, and deployments.
  • Azure Take a look at Plans: A software for creating and operating guide and automatic exams.
  • Azure Artifacts: A software for managing packages and dependencies.

Azure DevOps additionally integrates with different instruments and platforms, comparable to GitHub, Visible Studio Code, and now, Energy BI. This takes us to the subsequent part of this weblog submit, Integrating Energy BI with Azure DevOps.

Now that we perceive what Git and Azure DevOps are let’s see how we are able to combine Energy BI with Azure DevOps.

Integrating Energy BI with Azure DevOps has two completely different integrations. Cloud integration and native machine integration have the next necessities.

Conditions

To comply with together with this tutorial, you have to:

  • Within the cloud:
    • An Azure DevOps Service
    • A Energy BI account with one of many following licenses to allow Energy BI Workspace integration with Azure DevOps.:
      • Energy BI PPU (Premium Per Consumer)
      • Premium Capability
      • Embedded Capability (EM/A)
      • Material Capability
  • In your native machine:
    • The most recent model of Energy BI Desktop (June 2023 or later)
    • Both Visible Studio or VS Code

As acknowledged earlier, this submit explains the Cloud integration partTherefore, we require to have an Azure DevOps Service and a Energy BI account with a Premium licencing plan with a view to combine Energy BI with Azure DevOps.

In the following couple of sections, we glance into extra particulars and undergo them collectively step-by-step.

Azure DevOps Service

Proper off the bat, everybody with a private Microsoft account (sure, a private account comparable to Hotmail, MSN, Outlook, or Stay) or an organisational account can use Azure DevOps Service for free (as much as 5 customers). If you have already got an Azure DevOps Service, you may entry it by way of https://aex.dev.azure.com/ to see the present Organizations after passing you credentials, which appears like the next picture:

Azure DevOps Existing Organizations
Azure DevOps Current Organizations

If that is the primary time you’re logging into Azure DevOps, then you have to to offer some extra particulars, as proven within the following picture:

First login to Azure DevOps
First login to Azure DevOps

In Azure DevOps, Group refers to a logical container that hosts a set of tasks and assets. It serves as a top-level administrative unit that enables for managing and organising numerous groups, repositories, pipelines, and different artefacts associated to software program improvement and supply.
As talked about earlier, everybody can create an Azure DevOps account and consequently create new Organizations. Nonetheless, this freedom will be restricted. Learn extra right here.

Be aware:
Group names are globally distinctive as their generated URL follows the “https://dev.azure.com/{your_organization_name}” sample. Subsequently, it’s essential to plan on your organisation construction first.

If there aren’t any current organisations otherwise you do not need entry to any, you’ll see the next web page:
Azure DevOps Create New Organization
Azure DevOps Create New Group

Create New Group in Azure DevOps

Creating a brand new group is simple. Within the earlier picture, click on the Create new group button, then comply with these steps:

  1. On the Get began with Azure DevOps web page, click on Proceed

Get started with Azure DevOps
Get began with Azure DevOps

  1. Sort a reputation on your Azure DevOps group
  2. Choose a internet hosting Area. Attempt to choose the identical area internet hosting your Energy BI (Material) tenant. Extra on this later
  3. Enter the validation problem
  4. Click on the Proceed button

Creating a new organization in Azure DevOps
Creating a brand new group in Azure DevOps

  1. Enter a brand new Mission title
  2. Click on the Create challenge button

Creating a new project in Azure DevOps
Creating a brand new challenge in Azure DevOps

Thus far, we’ve created a brand new Azure DevOps account, outlined an group, and created a challenge. We are going to study later on this weblog that Energy BI and Azure DevOps integration occurs on the Workspace stage. Subsequently, utilizing the identical challenge title or much like the associated Workspace is sensible. With that, let’s proceed.

  1. Click on Repos. Our repo is empty at this stage
  2. Click on the Initialize button to initialise the primary department to the repo

Initialize main branch in an Azure DevOps Repo
Initialize the primary department in an Azure DevOps Repo

We’re all set now. Subsequent, we have to combine a Energy BI Workspace with our Azure DevOps.

Join Energy BI Workspace to Azure DevOps

Now that we efficiently configured Azure DevOps, it’s simple to attach Energy BI Workspaces to it. As acknowledged earlier, we are able to solely allow this function on Premium Workspaces (both PPU or a Premium capability).

If you have already got a Premium Workspace, then skip this part. In any other case, proceed studying.

Set Workspaces License

There are a number of methods to set a license to a Workspace. The next steps present a kind of strategies.

  1. In Energy BI Service, click on Workspaces
  2. Hover over the specified Workspace and click on the ellipsis button
  3. Click on Workspace settings
  4. Click on the Premium pane
  5. Choose the specified license
  6. Click on the Apply button

The next picture reveals the above steps:

Assigning Power BI Workspace to Premium Licenses
Assigning Energy BI Workspace to Premium Licenses

Configure Git Integration in Energy BI

Now that we’ve a Premium Workspace, let’s allow the Git Integration function.

Observe these steps:

  1. From Energy BI Service, click on Workspaces
  2. Hover over the specified Workspace and click on the ellipsis button
  3. Click on Workspace settings
  4. Click on the Git integration pane
  5. Choose an Group
  6. Choose the specified Mission
  7. Choose a Git repository
  8. Choose a Department
  9. Enter the title of the Git folder you need to combine the supported Energy BI artefacts
  10. Click on the Join and sync button

Be aware:

If you happen to get the “Unable to connect with Git department. This workspace is in a distinct area. Go to the workspace admin settings to allow cross-region connections.” error at this level, then soar to the subsequent part, the place I clarify how one can repair the problem.

Spoiler alert! You must be an admin to repair this, so in the event you aren’t, please contact your directors, and they need to have the ability to repair it for you. If you don’t get any errors, proceed studying.

  1. Energy BI asks on your affirmation if the folder doesn’t exist. Click on the Create and sync button

The next picture reveals the previous steps:

Git integration on a Power BI Premium Workspace
Git Integration on a Energy BI Premium Workspace

After efficiently synchronising the supported Energy BI artefacts within the Workspace with the Git repository, you need to see one thing like the next picture displaying the gadgets which can be synced and never supported.

Power BI Premium Workspace after syncing with Git repo on Azure DevOps
Energy BI Premium Workspace after syncing with Git repo on Azure DevOps

As you see, this web page has a number of adjustments, comparable to:

  1. A brand new Git standing added to the checklist view within the Workspace
  2. A brand new Supply management pane added
  3. Git sync data on the standing bar displaying the Linked department (the primary department in our instance), the Final synced time, and a hyperlink to the final Commit that the Workspace is in sync with.

Resolving the “Unable to connect with Git department. This workspace is in a distinct area. Go to the workspace admin settings to allow cross-region connections.” error

As identified within the earlier part, you could get the next error message when clicking the Join and sync button to combine your Workspace with Azure DevOps:

Fixing the Unable to connect to Git branch error in Power BI
Fixing the Unable to connect with Git department error in Energy BI

If you happen to face this error, it implies that your Energy BI tenant is in a distinct area than your Azure DevOps. That’s why I discussed earlier that it’s best to pick out the identical area as your Energy BI tenant when creating the Azure DevOps Group. To repair this challenge, you have to be a Material Administrator. If you happen to aren’t an admin, contact your administrator(s) to repair the problem. In any other case, comply with these steps:

  1. Click on the Settings gear from the highest proper of your browser

Be aware:

Relying in your display decision, you might even see an ellipsis button on the highest proper of your browser. Click on the ellipsis button, then click on Settings.

  1. Click on Admin portal
  2. Scroll all the best way down from the Tenant settings tab to search out the Git integration part. Develop the Customers can export gadgets to Git repositories in different geographical areas (Preview) setting
  3. Click on to toggle button to Allow it. (In my instance, I enabled this function to Your entire group. You could allow it just for Particular safety teams.)
  4. Click on the Apply button

The next picture reveals these steps:
Enabling Users can export items to Git repositories in other geographical locations feature in the Fabric Admin Portal
Enabling Customers can export gadgets to Git repositories in different geographical areas function within the Material Admin Portal

Now that we’ve allowed Git repositories to reside in a distinct geographical location than our Energy BI tenant, we are able to proceed the configuration from the place we left off.

This submit goals to cowl all points of Integrating Energy BI Premium Workspaces with Git repositories on Azure DevOps. I’ll publish a separate submit on utilizing this integration to synchronise our codes between Energy BI Service within the cloud and the Energy BI Desktop challenge on our native machine.

Keep tuned!

Related Articles

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Stay Connected

0FansLike
3,912FollowersFollow
0SubscribersSubscribe
- Advertisement -spot_img

Latest Articles