CSP
238 TopicsHowTo OMA-URI - something not working
Hi folks, i'm trying to experiment with OMA-URI within custom profiles. In this Use-case we're trying to achive, that we can manage Google Chrome Updates. Therefore i've downloaded the GoogleUpdate.admx and ingested it into the Intune custom profile. This is working, i'm able to see the admx at the clients registry under "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PolicyManager\AdmxInstalled" as well as the corresponding, possible values under ..\PolicyManager\AdmxDefault. Well, this looks good. Now i want to add the first setting to the custom profile. I had a look in ..\PolicyManager\AdmxDefault and found the value "ChromeUpdate~Policy~Cat_GoogleUpdate~Cat_Preferences\Pol_AutoUpdateCheckPeriod". Afterwards i've build the oma-uri path like this: ./Device/Vendor/MSFT/Policy/Config/ChromeUpdate~Policy~Cat_GoogleUpdate~Cat_Preferences/Pol_AutoUpdateCheckPeriod What i really don't get: How to find out what value type (and what spelling) is required? In this case i think it should be Integer and e.g. 60 (for 60 minutes). Unfortunatelly this setting is marked as "remediation failed".Solved26KViews0likes19CommentsAnnual/monthly price increase per 1st of April 2025
Hi Microsoft, Besides the discussion on the price increase itself: November 2024 announcements - Partner Center announcements | Microsoft Learn I'm wondering how this "standardizing the billing structure" works for triannual subscriptions. The post only states that Annual subscriptions with Monthly payment term will undergo a +5% price increase. But how will this affect multi-year subscriptions? Eg. Triannual subscription with annual payment term. Cheers, MartijnRegister for the next CSP Partner Technical Training!
The CSP Technical Training is designed to assist CSP Partners with technical implementation of change. Partners can expect to learn more about how to implement changes, get answers to technical questions and learn more API changes available in sandbox.14KViews0likes0CommentsToll-free numbers for Microsoft Teams now supported on NCE
We have exciting news! The New Commerce Experience (NCE) now supports the ability to acquire toll-free numbers for Microsoft Teams. Previously, customers would need to subscribe to Communication Credits to be able to acquire toll-free numbers for Audio Conferencing, auto attendant and call queue capabilities available with Microsoft Teams Phone. The requirement for Communication Credits had blocked customers on NCE from acquiring toll-free numbers. Please see the following guidance on how to acquire toll-free numbers on NCE. For customers who are moving from legacy (Communication Credits) to NCE or have already moved from legacy to NCE, partners will need to follow the steps below to ensure pay-as-you-go for toll-free numbers is set up correctly: Confirm that pay-as-you-go has been set up for the customer’s subscription: New commerce telco pay-as-you-go - Partner Center | Microsoft Learn Buy a pay-as-you-go calling plan for your Microsoft Teams subscription | Microsoft Learn Disable “Auto-recharge” for Communication Credits (if currently or previously on legacy) If the Communications Credit balance is zero, and telco pay-as-you-go has been configured for the customer by the CSP, then the commerce system will automatically move the customer to postpaid and the new meter will be validated. If the customer has a positive balance for Communications Credits, the commerce tool will be able to automatically identify this, and the remaining Communication Credits will be used for billing until the remaining balance is drained. Important note: Most customers have the “Auto-recharge” flag enabled within their account which will automatically refill their Communications Credit balance to whatever threshold level they configured it. You will need to disable this option if they wish to utilize the consumption meter; otherwise, the Communications Credit balance will indefinitely refill itself and the commerce system won't switch to the post-pay mechanism. See screenshots below for how to disable Auto-recharge. Resources New commerce telco pay-as-you-go - Partner Center | Microsoft Learn Buy a pay-as-you-go calling plan for your Microsoft Teams subscription | Microsoft Learn\ Read the Partner Center Announcement here: https://learn.microsoft.com/partner-center/announcements/2024-february#toll-free-numbers-for-microsoft-teams-now-supported-on-nce14KViews0likes0CommentsExpanded education partner opportunity with Copilot for Microsoft 365 | February 2024
Discover the expanded education partner opportunity with Copilot for Microsoft 365. Learn about the prerequisites, the CSP program, and the resources available for education partners to help customers become AI-powered organizations.11KViews2likes1CommentLegacy contract terms going away at renewal?
I am hearing that a customer currently on the old legacy CSP terms will be now forced into NCE terms at the renewal if that happens on or after July 1 2023. Can you provide guidance on and if legacy contracts currently enforce will be forced to NCE or will clients maintain the option to stay on legacy terms for the upcoming renewal? The NCE Playbook of course only defines what is current, which is that they can renew on legacy termsSolved7.7KViews0likes29CommentsCustom Policy CSP for NCSC Guidance for Windows 10
The NCSC Guidance for Deploying Intune managed Windows 10 clients (https://www.ncsc.gov.uk/guidance/eud-guidance-windows-10-1803-mobile-device-management) lists two custom OMA-URI settings that block unwanted devices from being installed. ./Device/Vendor/MSFT/Policy/Config/DeviceInstallation/PreventInstallationOfMatchingDeviceIDs ./Device/Vendor/MSFT/Policy/Config/DeviceInstallation/PreventInstallationOfMatchingDeviceSetupClasses Unfortunately the policy JSON that the NCSC supply is missing these settings. I tried to create the SyncML for both IDs using guidance from the Internet but I get a catastrophic failure error message in the logs and the policies do not apply. The settings that I have used are ./Device/Vendor/MSFT/Policy/Config/DeviceInstallation/PreventInstallationOfMatchingDeviceIDs <enabled/> <data id="DeviceInstall_IDs_Deny_List" value="PCI\CC_0C0A"/> <data id="DeviceInstall_IDs_Deny_Retroactive" value="1"/> ./Device/Vendor/MSFT/Policy/Config/DeviceInstallation/PreventInstallationOfMatchingDeviceSetupClasses <enabled/> <data id="DeviceInstall_Classes_Deny_Retroactive" value="1"/> <data id="DeviceInstall_Classes_Deny_List" value="{d48179be-ec20-11d1-b6b8-00c04fa372a7}{7ebefbc0-3200-11d2-b4c2-00a0C9697d07}{c06ff265-ae09-48f0-812c-16753d7cba83}{6bdd1fc1-810f-11d0-bec7-08002be2092f}"/> Has anyone successfully applied these settings using a custom device configuration policy? If so where am I going wrong? Any assistance will be gratefully receivedSolved6.7KViews0likes8Comments