Skip to main content

Beezzz Installation and Upgrade – Pre-Requisites

This article outlines the technical prerequisites and environment setup required before installing or upgrading the Beezzz software.

Before installing or upgrading the Beezzz software, ensure that all pre-requisites are met to support a smooth and efficient implementation. The list also covers the additional prerequisites for the DMA, which are listed separately at the end.
​

These requirements should be completed before the scheduled installation date.

Installation Sequence

The Development environment (TEST) is always installed or upgraded first.
After successful User Acceptance Testing (UAT), the Production environment will be scheduled for installation or upgrade.

Pre-requisites

Requirement

Details

Microsoft Service Account

Role:

  • Power Platform Administrator (or System Administrator and System Customizer roles at the environment level)

Licenses:

  • Power BI Pro

  • Power Apps Premium

  • Exchange Online Plan 1

  • Office E3

  • Teams

  • Naming Convention

    • The service account used for installation and configuration must follow the required naming format: [email protected]

Admin Center Security Role (for each environment)

Beezzz flows requires creating a new security role to assign permissions for the Beezzz environment Team. (this must be granted in each environment):

  • In the admin center, select the desired environment and create a new “security role”:

    • Name: Beezzz security role

    • Asing to it the proper Business Unit

    • Member’s privilege inheritance and select: “Direct user (Basic) access level and Team…”

    • Check the box of “Include App Opener…”

  • Once created, open the created Security role:

    • Under “Customization” dropdown

    • Search for the row “Process” and set all the permissions in that row to “Organization”

  • Finally, assign the security role to the Beezzz Team on the environment.

Power Platform Environments

Two Environments:

  • Test

  • Production

Naming Convention

  • Beezzz Test

  • Beezzz Production

Azure SQL Databases

Amount:

  • 3

Specifications:

  • Standard S1 for testing - 5GB

  • Standard S2 for production – 5GB

  • Standard S1 for jobs - 2GB

Naming Convention:

  • srv-Beezzz (server)

  • db-Beezzz-test

  • db-Beezzz-prod

  • db-Beezzz-jobs

Firewall Rule

Firewall rule on the Azure SQL Server used by Beezzz with the IP: 132.220.226.79 (Beezzz VPN).
​
The IP address will also be used to access Blob Storage, Power Apps and Power BI.

Blob Storage Account

Type:

  • StorageV2

Naming Convention:

  • Beezzz

Containers:

  • Uploads

  • Attachments

  • Masterdata-files

  • Pictures

Azure Security Groups

Two Groups:

  • Users

  • Admins

Naming Convention:

  • Beezzz Users

  • Beezzz Admins

App Registration with Power Apps Runtime Service

Permission:

  • user_impersonation

Power BI Workspaces

Two Power BI Workspaces:

  • Beezzz Test

  • Beezzz Production

Naming Convention:

  • Beezzz Test

  • Beezzz Production

Elastic Job Agent

This is required if you plan to run integrations with files containing more than a few thousand rows (depending also on the number of columns in the file).

Data Factory

This is required if you need custom pipelines to import data from APIs.

DMA pre-requisites

The DMA adds a survey portal on top of the standard Beezzz installation. The portal runs on Power Pages and is filled in by respondents from outside your organization, so it has a few extra requirements.

Complete these before the scheduled installation date.

Requirement

Details

Power Pages capacity

Buy or enable Power Pages capacity in your tenant.

This is the only net-new license the DMA requires on top of your standard Beezzz environment.

External respondent access

DMA surveys are completed by respondents outside your organization. The survey portal must be reachable by them, either anonymously through a token link or through login.

Confirm this is acceptable under your policies.

Dataverse Web API on the portal

The survey forms read and write through the Dataverse Web API.

This must be enabled on the portal.

Admin access during setup

A Power Platform or tenant admin must be available during setup to create site settings, configure the Web API, set table permissions, and sync the portal.

The build team needs temporary admin or maker access to complete this.

Firewall and conditional access

Any firewall or conditional access policy must allow portal access for the intended audience. Anonymous traffic from external respondents must not be blocked.

Did this answer your question?