I wanted to restrict the ability to add an account for Acrobat Reader DC to the following plist (com.adobe.Reader.plist) and create the file Jamf Pro's Application & Custom settings Payload, but the The restriction did not apply.

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

    <key>DC</key>

    <dict>

        <key>FeatureLockdown</key>

        <dict>

            <key>bUpdater</key>

            <false/>

            <key>cServices</key>

            <dict>

                <key>bToggleAdobeDocumentServices</key>

                <false/>

                <key>bToggleAdobeSign</key>

                <false/>

                <key>bTogglePrefsSync</key>

                <true/>

                <key>bToggleWebConnectors</key>

                <true/>

                <key>bUpdater</key>

                <false/>

            </dict>

            <key>cSharePoint</key>

            <dict>

                <key>bDisableSharePointFeatures</key>

                <true/>

            </dict>

        </dict>

    </dict>

</dict>

</plist>

However, when the same plist is directly stored in /Library/Preference, the restriction is applied.
I found out that the splist distributed from Application & Custom settings is stored in /Library/Managed Preference and the restriction is not applied.

In this case, what should I do if I want to distribute the splist from Jamf Pro to apply the restriction?
Please let me know if you have any good idea.

In addition, the target Mac is OSX 10.15.5, Application & Custom Settings payload, the Preference Domain is entered as "com.adobe.Reader".