This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(297.6, 33%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPJ%3C/text%3E%3C/svg%3E)
Hi, I am trying to extract the email attachments from a particular email account in my tenant using Azure Data Factory. Steps followed:
I am getting the following error:
ErrorCode=UserErrorOffice365DataLoaderError,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=Office365 data loading failed to execute. office365LoadErrorType: PermanentError. Provided application does not match the one in the token.,Source=Microsoft.DataTransfer.ClientLibrary,'
I have double checked everything. I have already created App client secrets multiple times and changed them everywhere.
Any help would be appreciated. Thanks
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(288, 61%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EP%3C/text%3E%3C/svg%3E)
Thanks for reaching out to Microsoft Q&A.
When generating secrets for your application in Azure, you don’t need to mention the Application ID during the secret creation process. The secret is tied to the application itself, so as long as you’re using the correct Application ID and the generated secret together in your linked service configuration, you should be fine.
Here are a few additional tips to ensure everything is set up correctly:
Secret Usage: Make sure that the secret you generated is being used in the correct linked service configuration. Sometimes, copying the secret incorrectly can lead to issues.
Permissions: Double-check that the permissions for the app are still valid and that admin consent has been granted. Sometimes, changes in permissions can take a moment to propagate.
Token Generation: If you’re manually generating tokens for testing, ensure that you’re using the correct Application ID and secret to obtain the token.
Logs and Monitoring: Check the Azure Data Factory logs for any additional error messages or details that might give more context to the issue.
If everything seems correct and you’re still facing issues, please do let us know
@Pushpak Jindal We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
@Pushpak Jindal just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
@phemanth Apologies for the delay in reply. I recreated App, tokens, permissions, etc. I started receiving the following error:
ErrorCode=UserErrorOffice365DataLoaderError,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=Office365 data loading failed to execute. office365LoadErrorType: PermanentError. Your application is not registered with MGDC. Please register your application following the instructions in aka.ms/mgdcdocs/onboardingexperience.
I got the Microsoft Graph Data Connect enabled to resolve the above error. Now, I have realized that I may not need MGDC for my use case.
Use case: To be able to read inbox (Message metadata, body, subject, attachments, etc.) of a particular email account in the organization. I believe the same can be achieved by using Microsoft Graph API and I don't need to use Microsoft Graph Data Connect.
To be honest, I am little confused now on the way forward. It would be helpful if you could suggest the right way forward based on my use case.
Thanks for reaching out to Microsoft Q&A
I understand how these issues can be quite complex. Based on your use case, it seems like using the Microsoft Graph API would indeed be a more straightforward solution for accessing email data, including message metadata, body, subject, and attachments, from a specific email account in your organization.
Here’s a suggested approach using the Microsoft Graph API:
App Registration:
Mail.Read, Mail.ReadBasic.All, and User.Read.Authentication:
API Requests:
To read emails, you can use the following endpoints:
GET /users/{user-id}/messagesGET /users/{user-id}/messages/{message-id}GET /users/{user-id}/messages/{message-id}/attachmentsHandling Responses:
For more detailed information and examples, you can refer to the Microsoft Graph API documentation.
Ensure that the Application ID used in the Office 365 Linked Service (LL1) matches exactly with the one in the token. Next make sure the token hasn't expired and is valid for the operations you're trying to perform.
@Vahid Ghafarpour Thank you for the prompt response. I have made sure that the Application ID is same. Although, I don't have to me tion any Application ID ehile generating secrets. I am generating sectets fot the particular application and using the same along with the respective Application ID. I hope I am doing the right thing.