Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
Please try again later.
Cannot change WebPart ExportMode to ‘All’. WebPart will be skipped (WebPart ID: <guid>)
To back up Classic Web Parts with the Modern App-Only Authentication method, Veeam Backup for Microsoft 365 requires setting the "Export Mode" property of the web part from "None" to "All" to make this Web Part exportable and available for backup.
Sometimes permissions or scale may make it challenging to configure "Export Mode". To automatically allow Veeam Backup for Microsoft 365 to mark a Web Part as exportable you must enable the "Allow custom script" option for affected SharePoint sites.
Important: Custom scripting support in SharePoint Online is changing, and so the content of this knowledge base article is subject to change.
Administrators have the option to allow execution of custom scripts. This setting is accessible in SharePoint Admin Center, under Settings -> Classic Settings.
It is also possible to enable custom scripting using PowerShell command:
Set-SPOTenant DenyAddAndCustomizePages $False
Learn more about custom scripting:
Microsoft has announced that starting in March of 2024, they will remove the ability to execute custom scripts on personal and self-service sites.
As part of the rollout of this change, Microsoft has created a new PowerShell command:
Set-SPO DelayDenyAddCustomizePagesEnforcement $True
This command is available in SharePoint Online Management Shell version 16.0.24524.12000 or later and allows administrators to delay the removal of custom script execution until May 2024.
Critical Note: Suppressing the warning will prevent the alert, and WebParts that would have triggered the warning will be skipped silently and not protected by Veeam Backup for Microsoft 365.
Before you begin:
Perform the following 4 steps on the Veeam Backup for Microsoft 365 server and each of the Proxies:
C:\ProgramData\Veeam\Backup365\Proxy.xml
<Source ShowSkippedSharePointWebPartsWarning="False" />
If the Proxy.xml already contains a <Source />
node, add the parameter ShowSkippedSharePointWebPartsWarning="False" after the existing parameters.
Do not create a second <Source />
line entry within the Proxy.xml file, it will not be read.
Your feedback has been received and will be reviewed.
Please try again later.
Please try select less.
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Your feedback has been received and will be reviewed.
Please try again later.