Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Log into the Azure Management Portal and go to the Azure Active Directory for your Office 365 tenant.
  2. Go to the Applications Azure Active Directory tab and select click the add button in the footer to manually add an ApplicationApp Registrations.
  3. Select "Add an application my organization is developing"New Application Registration".
  4. Give the application a name , and keep the default selection of "Web Application andApp / or Web API" and click the next arrow.
  5. Enter a Sign-on URL and App ID Uri (values of these don’t (the value of this doesn’t really matter other than being unique) and click next to create the application
  6. Click on the "Configure" tab and scroll to the bottom of the page to the section titled "Permissions to other applications"
  7. Click on "Add Application"
  8. "Create".
  9. Look for your new application on the Regitered Applications list and click it.
  10. Go to Required Permissions and click on "Add".
  11. On the "Select an API" section, add Add the "Office 365 SharePoint Online" application
  12. On Application "Select Permissions", select the following "Application Permissions":
    1. Read Managed Metadata.
    2. Have Full Control of all Site Collections.
    3. Read Items in all Site Collections. 
  13. After saving you have to click "Grant Permissions" to apply the changes.
Info
On the Configure section you'll also see the Client Application ID. Copy and save this ID, you are going to need it when configuring the connector.

...

  1. Click the Manage Manifest button in the footer and select "Download Manifest" to save the app manifest locally
  2. Open the downloaded manifest file and locate the empty keyCredentials attribute
  3. at the top of the Registered App Properties.
  4. Update the keyCredentials attribute with the following settings:

    Code Block
    languagetext
    themeRDark
    "keyCredentials": [
    	{
    		"customKeyIdentifier": "<$base64CertHash FROM ABOVE>",
    		"keyId": "<$KeyId FROM ABOVE>",
    		"type": "AsymmetricX509Cert",
    		"usage": "Verify",
    		"value": "<$base64Cert FROM ABOVE>"
    	}
    ],


  5. Save the updated manifest and upload it back into Windows Azure using the same Manage Manifest button in the footer (select "Upload Manifest" this time).

    Info
    Note: If you try to download the manifest again, you'll notice that the expiration dates are now there and the cert value is now null. This is normal and it shouldn't prevent the app to work as expected.


  6. Everything should now be setup in Azure AD for the app to run in the background and get app-only access tokens from Azure AD.

...