Outlook Fetch Command Line Sample

If you'd like to create this app from scratch using step-by-step instructions, see the tutorial.

To run this example, you need to create an app registration and update the code with your client ID and authorization URL.

Registering the app

In order to use the client credentials flow, the Outlook APIs require that you use a certificate for app authentication, rather than a client secret. Before we create the app registration in Azure, we'll start by creating a certificate.

As of this writing, the Azure v2.0 endpoints do not support the client credentials flow. So in order to use this flow, we need to register the app in the Azure Management portal and use the v1 token endpoint.

Create the certificate

The certificate must have a key length of at least 2048 bits, but it can be a self-issued certificate. On Windows, we can use the makecert.exe tool that's included with Visual Studio to create a certificate.

If makecert.exe is not on your PATH in a normal command prompt, you can open the Developer Command Prompt for VS2015 and run the commands from there.

From a command prompt, enter the following command, which creates the certificate in the current user's personal certificate store.

makecert -r –pe -n "CN=Outlook Fetch Sample Cert" –ss my –len 2048

Find the certificate in the user's personal certificate store in the Certificates MMC snap-in.
Press Windows key + R, then type mmc and hit enter.
On the File menu, choose Add/Remove Snap-in.
Select the Certificates snap-in and click Add.
Choose My user account and click Finish.
Click OK.
Expand the Certificates - Current User item in the left-hand list.
Expand Personal, then select Certificates.
Locate the Outlook Fetch Sample Cert entry in the list and select it.
Export the certificate with the private key. The app will need the private key to sign token requests.
On the Action menu, choose All Tasks, then Export.
On the Welcome screen, click Next.
Choose Yes, export the private key and click Next.
Make sure Personal Information Exchange - PKCS #12 (.PFX) is selected and click Next.
Choose Password and enter a strong password. Click Next.
Choose a location and file name and click Next. In this example we'll call this file outlook-fetch-priv.pfx.
Click Finish.
Export the certificate without the private key. We'll need this to attach to our app registration so Azure can use it to verify the app's signed token requests.
Make sure you still have the Outlook Fetch Sample Cert selected.
On the Action menu, choose All Tasks, then Export.
On the Welcome screen, click Next.
Choose No, do not export the private key and click Next.
Choose Base-64 encoded X.509 (.CER) and click Next.
Choose a location and file name and click Next. In this example we'll call this file outlook-fetch-pub.cer.
Click Finish.

Create the app registration

In this step we'll create an app registration in the Azure Active Directory associated with your Office 365 tenant. You'll need the credentials for an organizational administrator, and you'll need an Azure subscription associated with your Office 365 tenant. Instructions for associating an Azure subscription with Office 365 can be found on MSDN.

Browse to https://manage.windowsazure.com and sign in as an organizational administrator.
In the all items list, choose your Directory entry.
In the navigation menu at the top, choose APPLICATIONS.

On the bottom toolbar, choose ADD.

Choose Add an application my organization is developing.
Enter Outlook Fetch Sample for the name.
Make sure that WEB APPLICATION AND/OR WEB API is selected. Even though the app we are creating will be a console app, we still need to select this type. Click the Next button.
Enter http://localhost for the SIGN-ON URL.
Enter https://<your Office 365 domain>/outlook-fetch for the APP ID URI, replacing <your Office 365 domain> with your Office 365 domain. For example: https://contoso.onmicrosoft.com/outlook-fetch. Click the Complete button.
In the navigation menu at the top, choose CONFIGURE.

Locate the CLIENT ID. Copy this value and replace the YOUR CLIENT ID value in Program.cs with it.
Locate the permissions to other applications section. Click Add application.
Choose Office 365 Exchange Online and click the Complete button.
There should now be an entry for Office 365 Exchange Online in the permissions to other applications section. In the Application Permissions dropdown, select Read mail in all mailboxes, Read contacts in all mailboxes, and Read calendars in all mailboxes.

In the bottom toolbar, click SAVE. Wait for the update to complete.
In the bottom toolbar, click MANAGE MANIFEST, then choose Download Manifest. Save the manifest in the same directory as your certificate files, and rename it to appmanifest.json.

Upload public key to the app registration

In this step we'll insert the public key we exported earlier into the app manifest we downloaded, then upload the modified manifest back to Azure.

Download the Get-KeyCredentials.ps1 file and save it in the same directory as your certificate files.
Open Windows Powershell in the directory where you saved your certificate files.
Run the following command:

.\Get-KeyCredentials.ps1 .\outlook-fetch-pub.cer

Open the keyCredentials.txt file and verify that values were generated. It should look similar to this (values truncated):

"keyCredentials": [
  {
    "customKeyIdentifier": "Vr3TRhO85mjjJevziQrBk2nQnpE=",
    "keyId": "79a41b2e-85d1-49a2-8a81-d378b0eb8f9a",
    "type": "AsymmetricX509Cert",
    "usage": "Verify",
    "value": "MIIDKzCCAhOgAwIBAgIQ...1iukV2yc52g="
  }
],

Open the appmanifest.json file in a text editor. Locate the keyCredentials value:

"keyCredentials": [],

Replace the keyCredentials line in appmanifest.json with the entire contents of the keyCredentials.txt file. Save the file.
In the Configure page for the app registration in Azure Management Portal, click the MANAGE MANIFEST button and choose Upload Manifest. Browse to appmanifest.json and click OK to upload the updated manifest.
Before leaving the Azure Management Portal, click the VIEW ENDPOINTS button in the bottom toolbar. Copy the value of OAUTH 2.0 AUTHORIZATION ENDPOINT and replace the YOUR AUTHORIZATION ENDPOINT value in Program.cs with it.

Run the app