'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
Fix Outlook OneNote Button Opening the Wrong Microsoft 365 Group Notebook
Question details
Users are encountering a duplicate-file error or opening the incorrect notebook when clicking the Outlook OneNote button for a Microsoft 365 Group.
- Product
- Microsoft 365, Outlook, SharePoint
- Device & OS
- not provided
- Scenario
- A user clicks the Outlook OneNote button to access a Microsoft 365 group's default notebook after a notebook was copied into the SharePoint Site Assets folder via Power Automate.
- Observed behavior
- The Outlook button fails to recognize the copied notebook as the default group notebook and attempts to create another one, resulting in a duplicate-file error or opening the wrong file.
Ensure you have Microsoft 365 tenant administrator permissions and that the PnP PowerShell module is installed on your system before proceeding with the backend fixes.
Enable SiteNotebook via PnP PowerShell and Migrate Sections
Use this recommended workaround to natively generate a recognized default notebook and safely copy your sections into it using Power Automate.
The Outlook OneNote button relies on a standard Microsoft 365 group provisioning process to identify the default notebook. Notebooks copied by flows bypass this process. By forcing the SharePoint SiteNotebook feature to enable, the system will create the properly recognized notebook.
Launch PowerShell as an administrator and connect to your target SharePoint environment using PnP PowerShell commands.
Execute the command: Enable-PnPFeature -Identity f151bb39-7c3b-414f-bb36-6bf18872052f -Scope Web to forcibly enable the SharePoint SiteNotebook feature.
Wait a few moments and verify that the system has automatically generated the default OneNote notebook in the SharePoint Site Assets folder.
Set up a Power Automate flow to copy the necessary sections from your original customized notebook into this newly created, officially recognized default notebook.
Manually Create the Default Notebook in Site Assets
If you do not want to use PnP PowerShell, manually creating the notebook directly in the SharePoint interface avoids the flow-creation bug.
Contact Microsoft 365 Support
If neither workaround resolves the integration glitch, the issue may require tenant-level backend adjustments by Microsoft.
Switch to WPS Office for a Hassle-Free Document Experience
If complex Microsoft 365 integration errors are slowing down your team's workflow, consider WPS Office. It provides a lightweight, highly compatible alternative for document creation, spreadsheets, and presentations without the frustrating backend sync issues.
- 1. Download and Install: Get WPS Office Free from the official website and install it on your device in minutes.
- 2. Open Your Files: Launch the suite and open your existing .docx, .xlsx, or .pptx files with perfect formatting preservation.
- 3. Collaborate Easily: Use built-in cloud sharing features to collaborate with your team effortlessly, bypassing complex SharePoint permissions.
Frequently Asked Questions
Why does the Outlook OneNote button open the wrong group notebook?
The Outlook OneNote button is hard-coded to recognize notebooks created through the standard Microsoft 365 group provisioning process. If a notebook is copied into the Site Assets folder via a tool like Power Automate, the system does not recognize it as the default and will attempt to create a new one, causing errors.
Can I use Power Automate to set a copied notebook as the default?
No, there is currently no known PowerShell method or Power Automate action to change the default group notebook behavior once it has been merely copied. You must let the system create the default notebook natively and then copy your sections into it.
What is the PnP PowerShell command to force the creation of the SiteNotebook?
You can force the SiteNotebook feature by running: Enable-PnPFeature -Identity f151bb39-7c3b-414f-bb36-6bf18872052f -Scope Web. This triggers the correct backend generation of the group's default OneNote notebook.
