web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Customer experience | Sales, Customer Insights,... / OneNote integration
Customer experience | Sales, Customer Insights,...
Answered

OneNote integration

(4) ShareShare
ReportReport
Posted on by Jackie-20021515-0 105
Hello,
 
On the test and production environment we have turned off the OneNote integration.
 
What I did:
I went to Advanced settings > System > Document management > OneNote - Integration.
I turned off the OneNote integration per entity.
 
My question is:
When I turn the OneNote integration off for Account and Lead it creates an unmanaged layer on the Account entity and Lead entity (see screenshot). 
 
 
Is there a different way to turn off OneNote integration without creating a layer? And if so, how can I do this?
 
Many thanks in advance.
 
Jackie
Categories:
Microsoft Dynamics CRM
I have the same question (0)
  • Suggested answer
    Holly Huffman Profile Picture
    Holly Huffman 6,530 Super User 2025 Season 2 on at
    Good morning, afternoon, or evening – depending on where you are in the world!
     
    This issue you are describing—where disabling OneNote integration per entity results in an unmanaged layer—is expected behavior due to how entity-level settings are stored in the solution framework.
     
    When you disable OneNote integration via:
    • Advanced Settings > System > Document Management > OneNote Integration,
      and then turn it off per entity, it modifies the entity metadata directly, which creates an unmanaged customization layer on that entity.
    Unfortunately, there is currently no supported method to disable OneNote integration per entity without creating an unmanaged layer. This is because:
    • The setting is stored as part of the entity’s metadata.
    • Any change to that metadata (even toggling a feature) is tracked as a customization.
    Alternative approaches (with trade-offs):
    • Disable globally: You can disable OneNote integration at the system level (not per entity), which avoids touching individual entity metadata—but this removes it for all entities.
    • Use a managed solution: If you must disable it per entity and want to avoid unmanaged layers in production, consider making the change in a managed solution in a development environment and deploying it via ALM pipelines.
     
    I teamed up with AI to respond the most accurately and efficiently.
    Hope this helps some.
  • Jackie-20021515-0 Profile Picture
    Jackie-20021515-0 105 on at
    Hello Holly,
     
    Thank you for your answer. 
    How would you disable the OneNote integration globally or per environment? I can only turn the integration off per entity, following the below steps:
    Settings > System > Document Management > OneNote Integration.
     
    Kind regards,
    Jackie
  • Verified answer
    Jackie-20021515-0 Profile Picture
    Jackie-20021515-0 105 on at
    Update: We had layering issues. Microsoft layers were on top of our custom solution and the Microsoft layer enabled the OneNote integration for a few tables.
     
    What I did:
    1. Created a temporary solution called 'Temp solution' and I added the tables that had OneNote integration enabled. I made sure OneNote integration was turned off in the Temp solution.
    2. Exported the Temp solution from source and imported this managed solution in our target environments. Temp solution is top layer now.
    3. Removed the tables from our custom solution called 'XXX - customizations'.
    4. Exported the XXX - customizations solution from source and imported this managed solution in our target environments. The layer is removed in the managed environments.
    5. Added the same tables again with OneNote integration turned off into our XXX - Customizations solution. 
    6. Imported the XXX - Customizations solution back into the target environments (managed). The layer XXX - Customizations is the top layer again.
    7. Removed the Temp solution.
     
    It takes a while to do this, but it works.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
Tom_Gioielli Profile Picture

Tom_Gioielli 170 Super User 2025 Season 2

#2
#ManoVerse Profile Picture

#ManoVerse 61

#3
Gerardo Rentería García Profile Picture

Gerardo Rentería Ga... 52 Most Valuable Professional

Last 30 days Overall leaderboard

Featured topics

Hide selecting Contact for potential customer when creating quote

Product updates

Dynamics 365 release plans