Skip to content

Latest commit

 

History

History
154 lines (115 loc) · 9 KB

deployment.md

File metadata and controls

154 lines (115 loc) · 9 KB
Raw

Deployment Guide

Home About Deployment Guide Support

1. Pre-requisites

Core Solution:

  • A Service Account with an appropriate license for:

    • Power Automate
    • Microsoft Teams
    • Microsoft Exchange
    • SharePoint Online

  • A SharePoint list (covered further down 👇)

  • A Power Platform environment with Dataverse enabled

  • Teams Telephony Administrator, Teams Communication Administrator or Teams Administrator role.

  • Emergency Calling Policy

  • Network topology configured in Microsoft Teams

Emergency Locations:

When creating Emergency Locations for this solution, it is important to add Places, instead of using the Civic Address, as you are able to change the names of these after initial creation. Once a Civic address is created, it is validated and can not be modified, only deleted.

It is also important to link your subnets, Wi-Fi access points, Switches and ports to the Places that you create.

There is benefits in doing it this way, as you'll be able to define different zones of a building (Civic Address) to make more specific locations, if your IP subnets are configured this way.

Places within a Civic Address.

Subnets within a Place.

Note

You should use a naming convention with a static prefix to ensure all locations are captured, with a single string denoting the different locations, like a site reference. [PREFIX] [LOCATION IDENTIFIER] (e.g. Loc SOUTHAMPTON)

Find out more about the Network topology requirements here

Add-ons:

If you choose to extend your Emergency Calling notifications beyond just email, you may also need:

When extending further beyond the core solution, you can add more columns to the SharePoint list to hold different data for each site.

E.g. a mobile number for SMS.

When making changes to the Power Automate Flow, open all conditions and Apply to each and place any extra action beneath the "Send an email (V2)" action.

Select the column you created as the "To:" address, and it's best to use the SiteSearch variable for the content, as this has been converted to plain text. (You may see that an Apply to each action is created, don't panic! This is normal)

Note

Be sure to use the Unmanaged Solution if you are looking to make changes to the solution.
If you choose to use Power Automate premium connectors, you'll need to license these too or use a Pay-as-you-go Power Platform plan. More information about PAYG.

2. Configuration

Creating the SharePoint List

The first thing you'll need to decide is where to host the SharePoint list holding the data for this solution.

For the purpose of this guide, I have created a new Team in Microsoft Teams called Emergency Notifications, and I will use this SharePoint site to host my SharePoint list.

  1. Navigate to the SharePoint site you have chosen to host the SharePoint list.
  2. Click the "+ New" button.
  3. Select "Blank List".
  4. Give your list an appropriate name (I'm using SiteList)
  5. Once created, click the gear in the top right hand corner, and select List settings.
  6. Under Columns, select the "Title" column.
  7. Rename the column's name to "SiteRef".
  8. Toggle "Require that this column contains information" to Yes.
  9. Toggle " Enforce unique values" to Yes.
  10. Press OK in the bottom right corner of the window.
  11. Click "Create column".
  12. Name the column "Email".
  13. Toggle "Require that this column contains information" to Yes.
  14. Press OK in the bottom right corner of the window.

Deploying the Power App Solution

  1. Download the Solution export.
    Version Notes
    Managed Solution If you're only looking to use the Core Solution.
    Unmanaged Solution If you're looking to tweek/extend the solution further.
  2. Nagivate to Power Apps. Remember to sign in with the Service Account you created above.
  3. From the left rail, select Solutions
  4. Select "Import Solution"
  5. Click "Browse"
  6. Select the downloaded solution.
  7. Click "Next"
  8. Click "Next" again.
  9. Verify and sign in to the connectors.
  10. Click "Next"
  11. For 'SPOSite', select the SharePoint site where your list resides.
  12. For 'SPOList', select your list
  13. For Site Prefix, enter the Prefix as detailed in the pre-requisites.
  14. Click "Import".

Configure Teams Emergency Calling policies

Now that you've imported the solution, you need to set your Teams Emergency calling policy to send the notification to the Service Account, linked above.

To do this:

  1. Log in to the Teams Admin Center.
  2. Navigate to Voice > Emergency policies on the left rail.
  3. Select the Global policy.
  4. Under Emergency numbers, click "Add"
  5. Change Notification mode to "Send notification only".
  6. Search for your Service Account, click add.
  7. Click "Apply".

Page info

Page Deployment Guide
Author Rob Watts (@robwatts365)
Version 1.0
Date 17/06/2024