Home > Back-end >  Linked Service Microsoft office inside a Managed Virtual Network or REST API
Linked Service Microsoft office inside a Managed Virtual Network or REST API

Time:02-08

Hopefully someone will have some experience of trying similar things and can offer some help.

Background

I have an Azure Synapse Analytics Workspace inside a Managed Virtual Network with Data Exfiltration Protection enabled. Public network access has been disabled. I have a customer VNET to with Private endpoints and a Virtual Machine to connect to the workspace. This works fine and I can connect to and configure a range of services e.g.:

  • Azure SQL
  • On-premises SQL using a Self Hosted IR
  • Azure Key Safe

So I'm comfortable with the concepts in general.

I have questions about connecting to other sources.

Connections

Connections to Microsoft Office for the collection of Graph data.

I have POC on another Synapse Workspace that collects BasicDataSet_v0.Message_v0 and BasicDataSet_v0.User_v0. However when I attempt to connect to the Microsoft Office Connection as a linked service from within the Managed Virtual Network I cannot connect.

{
    "name": "Office3651",
    "type": "Microsoft.Synapse/workspaces/linkedservices",
    "properties": {
        "annotations": [],
        "type": "Office365",
        "typeProperties": {
            "office365TenantId": "[TENANT GUID]",
            "servicePrincipalTenantId": "[TENANT GUID]",
            "servicePrincipalId": "[SERVICE PRINCIPAL GUID]",
            "encryptedCredential": "ew0KICAiVmVyc2lvbiI6ICIyMDE3LTExLTMwIiwNCiAgIlByb3RlY3Rpb25Nb2RlIjogIktleSIsDQogICJTZWNyZXRDb250ZW50VHlwZSI6ICJQbGFpbnRleHQiLA0KICAiQ3JlZGVudGlhbElkIjogIlNZTkFQU0VAQUJFNEVBODktM0E5MS00RjExLTgzOTItMjcyOURFNTY2NDk3XzhhMGViNzIyLTRmNTAtNGQ4Zi1iYTVhLTYwYWNiNzQyYjMzMiINCn0="
        },
        "connectVia": {
            "referenceName": "AutoResolveIntegrationRuntime",
            "type": "IntegrationRuntimeReference"
        }
    }
}

The error I get attempting to validate the connection is:

One or more errors occurred.
An error occurred while sending the request.
Unable to connect to the remote server
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 51.105.5.65:443
Activity ID: 218a9020-6de9-4436-b61b-0e62c6b9c147.

As indicated I can get this to work without a Managed VNET.

I get similar experiences for REST Api connections, these are connections which I have used outside of a Manage VNET

The connection to the REST service failed. Endpoint=https://***URL***/, Reason=.
A task was canceled.
Activity ID: 7bc36bd7-d135-4636-8303-89acc84ef711.

Request

If anyone has tried similar or has found documentation for a more detailed exploration of how to create linked services I would be very grateful. It becomes harder to justify the use of the Managed VNET if these are hard limitations.

CodePudding user response:

I have experimented with this and find that the limiting technology is the use of the Data Exfiltration Protection. If I provision a Managed Virtual Network on the Synapse environment I find that I am able to connect, and extract data from REST endpoints and from Microsoft Office.

  •  Tags:  
  • Related