On Premises

How to connect to Azure SQL

Note

Azure Private Link (aka Private Endpoint as described by Microsoft here) is not supported.

AnywhereNow needs to directly connect to Azure SQL database(s) in your Azure tenant A dedicated and trusted instance of Azure AD. The tenant is automatically created when your organization signs up for a Microsoft cloud service subscription, such as Microsoft 365. An Azure tenant represents a single organization. [Taken from Microsoft Docs] for your CDR Call Detail Records (CDR) are the meta data of a converstation: who talked to whom, at which time, for how long and with which identity among other things (skill, optional classification, etc) which gets stored in your SQL (analytical) database. data to be stored and retrieved. If Dialogue Manager is used, an additional Azure SQL database is needed for the conversational (text) message data and history.

CDR and DialogueManager each require their own database.

Scenarios

Prerequistes

  • An Azure SQL database per region: recommended at least S1 20DTU during project initiation (and is typically sufficient for Golive to production, but exceptions may apply, see warning below)
  • Azure SQL DB is remotely accessible
  • SQL user account (for SQL authentication): which is database owner
    • For access to the CDR database a Microsoft Entra account (for Microsoft Entra authentication) is also supported.
  • Connection string to the database(s): Only the formats provided below are supported (i.e. only connections directly to <server>.database.windows.net and the other parameters are required).
  • Firewall allowance for regional Dialogue Cloud IP address: will be provided by your AnywhereNow contact.

Note

After Go-live, maintenance and regular monitoring of the database(s) is the customer's responsibility.

Creating an account

You can choose between:

  • Option 1 (Preferred): Azure SQL Account (supported by all AnywhereNow applications)

    Note

    The Dialogue Manager requires a SQL Account in the Connection string for the DialogueManager database (see below). All other applications (Core, UTL and Classification) support more options.

  • Option 2: Microsoft Entra ID Formerly known as Azure Active Directory (or Azure AD, or AAD) account (Supported by Core, UniversalTimeLine and Classification services)

    Note

    Supported for the Core UCC Service, Universal Timeline Service and the Call Classification Service which share the same ConnectionString. NOT supported for Dialogue Manager Service.

Below a guideline on how to create these accounts (Choose the one that is needed).