Storage Hosted on Customer Azure Blob

If you require control and ownership of your stored Meeting Insights data, you can use Meeting Insights Bring Your Own Blob Storage (BYOS) feature to use your Azure Blob Storage account across different locations (regions). After configuring BYOS for each location (region), you can assign these storage accounts to specific User Profiles, ensuring that recordings for users associated with these profiles are stored in the designated storage locations.

Adding BYOS storage includes the following main steps:

1. Setting up your Azure Blob storage account.
2. Configuring Meeting Insights with your storage account (BYOS).
● Bring Your Own Blob Storage requires the BYOS feature key. Contact your Service Provider if it's not available in your Meeting Insights application.
● Make sure that your BYOS accounts are registered on your Microsoft 365 tenant.
● Performance latency may occur if the storage location is geographically distant from the Meeting Insights deployment instance.
● The customer’s user information such as Display name, email, Azure OID, and recorded meeting metadata such as time, duration, subject, participants, and invitees are stored in the Meeting Insights separate database per customer.
● When a user is assigned to multiple user profiles, all profiles must be configured with the same storage. User recordings will be stored in arbitrary storage locations if the user is assigned to user profiles with distinct storage locations.
● You can delete an added BYOS storage only when there are no active meeting recordings.

Defining Your Azure Blob Storage Account

Before you can configure Meeting Insights with BYOS, the first step is to configure a storage container in your Azure Blob Storage account. This process includes generating a Shared Access Signature (SAS) token and URL, which you'll need later when configuring BYOS in Meeting Insights. In addition, this process includes specifying a start date and time, as well as an expiry date and time for the SAS token.

This section assumes that you have an Azure Blob Storage account with a storage container.

➢ Set up Azure Blob Storage account:
1. Log in to your (customer tenant) Microsoft Azure portal account.
2. Access the Storage accounts page, and then select the relevant Blob Storage account.
3. Navigate to Data storage > Containers, and then select the container where you want to store media.
4. Right-click the container, and then from the drop-down menu, choose Generate SAS; the Generate SAS dialog box opens.

5. In the Generate SAS dialog box, configure access settings to the storage:
a. Under the Signing method group, select the Account key option.
b. From the 'Signing key' drop-down list, select Key 1.
c. From the 'Stored access policy' drop-down list, select a shared access policy.
d. From the 'Permissions' drop-down list, select (check) all the listed permissions check boxes.
e. In the 'Start' and 'Expiry' fields, define the start and expiry time-date of the signed key, respectively.

For Meeting Insights' BYOC, the SAS token expiration period must be at least three months.

f. Under the Allowed protocols group, select the HTTPS only option to allow only requests using the HTTPS protocol.
g. Click the Generate SAS token and URL button; a shared access signature (SAS) token and URL are generated and displayed in the fields below the button:

6. Copy and paste the Blob SAS URL in a secure location (e.g., in Notepad). You'll need this URL (which includes the SAS token key) when configuring this BYOS storage in Meeting Insights (see Configuring Meeting Insights with BYOS).

Configuring Meeting Insights with BYOS

Once you have configured your Azure Blob Storage account and generated a SAS URL, you can configure Meeting Insights with a BYOS.

Meeting Insights doesn't display BYOS storage capacity. Storage monitoring can only be done through your Azure Blob storage account.

➢ To configure Meeting Insights with BYOS:
1. Under the ‘System Settings’ menu, click the Storage option; the default storage account is displayed (e.g., Europe LRS).
2. Click the Bring Your Own Blob Storage button; the following dialog box appears:

3. In the 'Friendly Name' field, type a meaningful name for your Blob storage container so that you can easily identify it later, especially useful if add multiple Blob storage containers (e.g., "West US BYOS" or "North Europe BYOS").
4. In the 'Blob SAS URL' field, paste the Blob SAS URL (also contains the SAS token key) that you copied from your Azure Blob Storage account (see Defining Your Azure Blob Storage Account).
5. Click Apply; the BYOS is added to Meeting Insights:

6. Associate the BYOS account to a Users Profile, by selecting it from the 'Select Storage' drop-down list, as described in User Profiles.

For monitoring the storage connectivity status, see Monitoring Storage Connectivity Status and Capacity.

Connectivity Issues to BYOS Storage

If Meeting Insights is unable to access the BYOS storage, it deletes the recording after several retry attempts. Loss of connectivity to the BYOS storage can occur for several reasons, such as:

■ Storage no longer exists
■ Network issues
■ SAS token key expired

Meeting Insights notifies you about the upcoming token key expiration at 30 days, 7 days, and on expiration day, both via email and in the system activity logs. In addition, Meeting Insights triggers an alarm if the connection to the storage is lost or the token key expires.

● The SAS token key expiration period must be at least three months.
● To prevent outages and the potential loss of recordings, it's essential that you generate a new SAS token key before it expires and update Meeting Insights with the new key.