csp
243 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.8KViews0likes29CommentsMicrosoft CSP - Indirect Reseller Status is Suspended and Can't Get Fixed
I am in a very bad spot with our indirect reseller Microsoft account and am hoping that maybe someone out there might be able to help me. In mid May, I placed an order with Pax8 for a new customer and the order was rejected by Microsoft with the error, "Associated partner LegalBusinessProfile NotFound." It turns out that when we moved offices and I updated our business's address at http://partner.microsoft.com, Microsoft de-authorized our partner status, which I didn't catch, and then put our Cloud Service Provider (CSP) indirect reseller program into "Suspended" status after some time. In the partner center, I was able to get our legal business profile fixed easy enough - I just had to open a ticket and send them some legal documentation. Everything under the "Partner" tab in the Partner Portal is now green checkboxes and "Authorized". Pax8 tried the provisioning again, and got the same error. It turns out that our "Indirect Reseller status" is now "Suspended" and this wasn't changed when the "Partner" status was fixed. Microsoft has a webpage that describes why this can happen and what to do to get it fixed at https://learn.microsoft.com/en-us/partner-center/account-settings/suspended-partner-center-account . It says, "Microsoft suspends Partner Center accounts for Microsoft AI Cloud Partner Program when: Significant account abuse is detected Your vetting status is Rejected for more than 30 days" We haven't had any account abuse (mercifully, our existing tenants are still operational and being billed for through Pax8), so our vetting status was almost certainly to blame. That same document says, "If you are sure that your account is compliant and should be moved back to Active state, contact https://partner.microsoft.com/dashboard/support/servicerequests/create for help with reactivating your account," so I opened a ticket with Microsoft. Actually, 3 tickets so far, because every single one has the same copy-and-paste reply: Thank you for contacting Microsoft Partner support about the suspension of the CSP account. In the Microsoft AI Cloud Partner Program Agreement, both Microsoft and our partners reserve the right to walk away from the partner relationship by providing 30 days' notice to the other. The notice of suspension and termination proceeding was provided April 2024. Neither party is required to offer an explanation for the decision to terminate the partner agreement. As Microsoft is exercising its rights under this section 4.b of the Microsoft AI Cloud Program Agreement, we are unable to share an explanation or further details. Thanks, I can't get anywhere with Microsoft support. We just landed a big customer and need to set up their tenant. I am afraid that if this goes on much longer or if somehow we are unable to add any more customers to our Pax8 account, that we'll lose this customer, which is large enough to really hurt the business. Does anyone here have any ideas on how to get through to someone at Microsoft that could help with this situation? Does anyone else have any other ideas on what else we could try? Some additional notes: When clicking "Agreements" in the partner portal, we get an error message, "Service unavailable. Something went wrong. Please try reloading the page, if this problem persists please contact https://go.microsoft.com/fwlink/p/?linkid=868372." Everything in Legal Info/Partner looks good. Our "Microsoft AI Cloud Partner Program status" is "Active". Everything in Legal Info/Reseller looks good except that "Indirect Reseller status" shows "Suspended". Under Identifiers/Microsoft AI Cloud Partner Program, I have 1 PartnerGlobal ID and 2 PartnerLocation IDs, corresponding to our old and new addresses. Do I need to delete the old PartnerLocation ID? I haven't done so because it looks like this step is irreversible but I am getting desperate enough to try it. Our "Company profile" is not filled out, but the "Update" button stays grayed out after I fill in the information and it appears that I am unable to update this. I thought that maybe I just needed to sign the "Microsoft AI Cloud Partner Program Agreement" again, but I can't find anywhere on the partner portal where I would do so. I went through my emails exhaustively and we did not receive a, "notice of suspension and termination proceeding" in April 2024, or any other time for that matter. I can't find a copy of the Microsoft AI Cloud Program Agreement to even see what section 4.b says. I've dealt with government bureaucracies a lot in my career, but I've never experienced a Kafkaesque situation 10% as bad as this one. This is probably the most stressful thing I've dealt with in this business in the last decade. This could destroy our business if I can't get this sorted out. Sorry for the wall of text, but I tried to include as much detail as possible and it got long. If you got to this point in my post, thank you for helping or trying to help me. The latest ticket ID we have from Microsoft is 2406050040012239Solved