Skip to content

Commit e6a03c1

Browse files
authored
Updated connector documentation (#3749)
1 parent 8557006 commit e6a03c1

File tree

2 files changed

+11
-11
lines changed

2 files changed

+11
-11
lines changed

certified-connectors/dox42/README.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,32 +1,32 @@
11
## dox42 connector
2-
dox42 provides a powerful and very extensive REST API. Using dox42 you can automatically generate documents with data from all sources, like D365, SharePoint or others. dox42 uses Azure Active Directory for authentication.
2+
dox42 provides a powerful and very extensive REST API. Using dox42 you can automatically generate documents with data from all sources, like Dataverse, SharePoint or others. dox42 uses Microsoft Entra ID for authentication.
33

44

55
## Prerequisites
66
You will need the following to proceed:
77
* A Microsoft Power Apps or Power Automate plan
8-
* Azure Active Directory
8+
* Microsoft Entra ID
99
* a dox42 license (dox42 Online or dox42 Server + dox42 Word/Excel/PowerPoint Add-ins)
1010
* dox42 Server Designer application (Version 1.0.1.4 or later)
1111

1212
## Building the connector
13-
Since dox42 uses Azure Active Directory (AD) authentication, we first need to set up a few things in Azure AD so that our connectors can securely generate your documents with dox42. After that is completed, you can test the connector.
13+
Since dox42 uses Microsoft Entra ID authentication, we first need to set up a few things in Microsoft Entra ID so that our connectors can securely generate your documents with dox42. After that is completed, you can test the connector.
1414

15-
### Set up an Azure AD application for your custom connector
16-
We first need to register dox42 as an application in Azure AD. This will allow the connector to identify itself to Azure AD so that it can ask for permissions to access your data on behalf of the end user. You can read more about this [here](https://docs.microsoft.com/en-us/azure/active-directory/develop/authentication-scenarios) and follow the steps below:
15+
### Set up an Microsoft Entra ID application for your custom connector
16+
We first need to register dox42 as an application in Microsoft Entra ID. This will allow the connector to identify itself to Microsoft Entra ID so that it can ask for permissions to access your data on behalf of the end user. You can read more about this [here](https://docs.microsoft.com/en-us/azure/active-directory/develop/authentication-scenarios) and follow the steps below:
1717

18-
1. Create an Azure AD application
19-
This Azure AD application will be used to identify the connector to dox42. This can be done using [Azure Portal] (https://portal.azure.com), by following the steps [here](https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-register-app). Once created, note down the value of Application (Client) ID. You will need this later.
18+
1. Create an Microsoft Entra ID application
19+
This Microsoft Entra ID application will be used to identify the connector to dox42. This can be done using [Azure Portal] (https://portal.azure.com), by following the steps [here](https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-register-app). Once created, note down the value of Application (Client) ID. You will need this later.
2020

21-
2. Configure (Update) your Azure AD application to use the dox42 connector:
21+
2. Configure (Update) your Microsoft Entra ID application to use the dox42 connector:
2222
This step will ensure that your application can successfully retrieve an access token to invoke dox42 on behalf of your users. To do this, follow the steps [here](https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-configure-app-access-web-apis).
2323
- For redirect URI, use “https://global.consent.azure-apim.net/redirect”
2424
- For the credentials, use a client secret (and not certificates). Remember to note the secret down, you will need this later and it is shown only once.
2525
- For API permissions, make sure that the necessary permissions like delegated SharePoint permissions and for example “Dynamics CRM user_impersonation” are added.
26-
- Follow the instructions in chapter 6 of the dox42 AAD Documentation: https://www.dox42.com/Download/dox42_DynamicsCRM_Documentation_EN.pdf
26+
- Follow the instructions in chapter 6 of the dox42 Microsoft Entra ID Documentation: https://www.dox42.com/Download/dox42_DynamicsCRM_Documentation_EN.pdf
2727

2828

29-
### At this point, we now have a valid Azure AD application that can be used to get permissions from end users and access dox42 document generation. The next step for us is to modify the premium connector.
29+
### At this point, we now have a valid Microsoft Entra ID application that can be used to get permissions from end users and access dox42 document generation. The next step for us is to modify the premium connector.
3030

3131
- Enter your Azure Active Directory Information in the Security tab of the connector. Follow the Security information in the dox42 Power Automate Documentation for further information: https://www.dox42.com/Download/dox42_MSPowerAutomate_LogicApps.pdf
3232

certified-connectors/dox42/apiDefinition.swagger.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
"swagger": "2.0",
33
"info": {
44
"title": "dox42",
5-
"description": "The dox42 connector provides a connection to the very extensive dox42 REST API and allows you to automatically generate documents in a flow with data from all sources, like D365, SharePoint or others.",
5+
"description": "The dox42 connector provides a connection to the very extensive dox42 REST API and allows you to automatically generate documents in a flow with data from all sources, like Dataverse, SharePoint or others.",
66
"version": "1.0",
77
"contact": {
88
"name": "dox42 Support",

0 commit comments

Comments
 (0)