User Profile
MartijnBreet
Iron Contributor
Joined May 25, 2018
User Widgets
Recent Discussions
Re: Renew CSP subscription
Hello Max, In general this seems legit. You/your company bought licenses from a partner to use as an endcustomer. Subscriptions can differ in term, and it is very considerate of the partner to contact you/your company as the customer and inform if you would like to enter a new subscription term. What does it say in the contract with that partner with regards to renewal? KInd regards, MartijnRe: I have a question about upcoming FY26 on the Distributor side minimum of 30 million USD TTM billed.
Hi JenRheault , Thanks for the documentation. Quick question on the disti doc: it reads 'multiple authorized PGA's exits' shouldn't this be 'multiple authorized PLA's exist'? (page 5 of CSP Eligibility Requirements for Distributors doc) Other question: Can we determine based on the same last sentence that IF more than 1 PLA exists under a single PGA; all these PLA's need to meet the Disti requirements in January? (regardless of when the first tenant was operational in the past) Thnx & kind regards, MartijnRe: Deployments calculation for Modern Work
Hi Esben, Few comments: You link the deployments score to qualifying for membership, however deployments count for solution partner designations, not membership. With the Modern work you need three indicators to go up: number of customers ('customer adds') (measured in #tenants) number of TENANTS which have workloads deployed ('deployments') reaching at least 40% MAU number of active USERS across all tenants need to increase compared to year before (MAU growth) The general concept of these metrics is flawed in the long run anyhow, because it becomes nearly impossible to grow year on year on year. Certainly considering growth is naturally capped at 100% of licenses and orgs would need to grow/buy more licenses to be able to grow in MAU. For the SMB track all customer tenants between 11 - 300 seats count. When adding customers they are preferably spread across various industries with high/lows in different months...in that case you might be able to mitigate the patterns which occur a bit. Regards, MartijnRe: CSP Direct Bill Partner Profitability Estimator
OpsReadiness... https://partner.microsoft.com/en-GB/asset/collection/microsoft-commerce-incentive-resources#/?page=2 (alternative route: via https://partner.microsoft.com/dashboard/v2/incentives/enrollment/summary and then the link to resources, in this case for the MCI program) Regards, Martijnsuggestions for logo/letterbuilder
Dear Microsoft, fellow partners, Partnercenter (benefits section / logo builder at https://partner.microsoft.com/en-us/dashboard/mpn/membership/benefits/logobuilder) offers various documents partners can use to prove their status within the MCAIPP (formerly MPN). These ‘letters’ are similar in setup, but not quite and differ in important aspects which requires these letters to be generated more often that really needed… Legacy letter The legacy competency letter has no enddate (hurray!) MAF letter Valid for 3 months (90 days) Must add 1 sku (?) Requires customer details Requires tender reference Only for non-CSP authorizations/VL ? (MPSA, Enterprise Direct Advisor, EES etc) SPD letter Asks customer details (not required like with MAF) Includes ALL or None of business locations (as opposed to selection in the MAF letter) Only valid for a month (30 days) If we have requests for these letters spread evenly over the year we are required to keep generating a new letter every Q or M depending on what is asked for; while details remain unchanged (except for the date) The Microsoft partnership is renewed once a year, and valid for a year. Any SPD’s attained are also held until next renewal, so there is no apparent need to limit the validity of either proof to a period which isn’t even related to the membership year. Despite that, current properties of the letters ignore these facts leading to unnecessary burden for partners. We have the following suggestions: MAF Remove 90 day period in MAF letter / coterm with membership year* Remove need to add a sku Remove need for adding customer details Remove need for tender reference Optionally also add the CSP authorization based on signed MPA in the MAF as this will be the motion going forward (or would Microsoft prefer to create a separate letter for that…?) SPD: Remove 1 month validity / coterm with membership year* Remove need for customer details Make ‘None’, ‘All’ or selected locations visible on letter *Alternative: list the membership year for the partner, so customers know that between moment of payment for new program year / next years renewal we hold certain authorizations and/or status. (month x until month y next year) With regards to renewal process: could Microsoft please revert to the OLD system, where a partner renews before membership expires? Currently as soon as a partner initiates renewal; the attained SPD’s drop off (also visible in the business profile listing) only to reappear after payment has been received. With regards to the payment process: when do you expect your system to be able to identify the unique combination of Partner ID + Order ID when sending a payment for membership fee; by reading the payment description field? (that would save every partner & their Finance department creating ‘proof of payment’ which is to be uploaded to complete the renewal….) General remarks: Why is it Dan Rippey handing out the solutions partner certified letter, but when we request the Solutions partner congratulatory letter its signed by Nicole Dezen? Kind regards, MartijnRe: security score requirements > 80 ?
I need to have my cat watch Microsoft for every move they make. Now the wordings around the security requirements have changed. https://learn.microsoft.com/en-us/partner-center/security/security-requirements Beginning October 1, 2025, updated Cloud Solution Provider (CSP) authorization eligibility requirements will be enforced for direct bill partners, distributors (formerly indirect provider), and indirect resellers. These changes are designed to strengthen the security posture and operational readiness of partners across the ecosystem. As part of these updates, all partners must meet the mandatory security requirements of the Partner Center security score: Enable Multi-Factor Authentication (MFA) for all administrative users in the CSP tenant. Designate a security contact within Partner Center. Respond to security alerts within 24 hours or less. (doesn't apply to indirect reseller partners). These requirements are validated annually during the anniversary month of the partner’s original CSP onboarding. it used to be 1, 2 & 3 go into effect per 1-10-2025, now its shifted towards anniversary. never a dull moment. Thnx for making me aware. regards, MartijnRe: security score requirements > 80 ?
Hi Nam, Based on my interpretation there are different requirements (policies) which need to be in effect at certain moments in time. Starting 1st of October 2025 all partners need to have at least the following policies in place: Enable multifactor authentication for admin roles in the Partner tenant Response to alerts is 24 hours or less on average Provide a Security contact at anniversary month other requirements need to be met: Direct Bill anniversary 4. Enable MFA for all Customer Admin roles 5. All azure subs have spending limit Same policy 4 & 5 apply for the Disti, but as the FAQ mentions they only need to meet the revenue and security requirements on anniversary in Year 2. Applying all above with current scores brings tenant to 80 points. In preview I can see another policy in Partnercenter worth 10 points, then we are still missing 10 points for a yet undisclosed requirement. 6. All users complete multifactor authentication registration 7. Yet unknown requirement As said, this is my interpretation of the documentation. Hope this helps, but it wouldn't mind to keeping an eye on partnercenter on any changes popping up there... Regards, Martijn ps: readable version of the FAQ in CSP partner launch calender https://partner.microsoft.com/nl-nl/resources/detail/partner-launch-calendar-csp-pdfRe: Unable to login to Azure (blocked tenant)
probably not assuming the tenant went into inactive state more than 20 days ago. https://learn.microsoft.com/en-us/entra/fundamentals/inaccessible-tenant result is: The tenant is deleted after 20 days of being inaccessible due to inactivity and it isn't recoverable.Re: Azure Consumption / Microsoft CSP Maximum Earning
Hi Charlie, The most recent version of the MCI guide (see https://partner.microsoft.com/en-GB/asset/collection/microsoft-commerce-incentive-resources#/) does not include information on CSP maximum opportunity details, but the September 2024 one did. Its per location ID, customer ID + product, so you wont hit the max very soon. under https://partner.microsoft.com/dashboard/v2/earnings/reports > New report > Maxcap balance you can find out where you stand. Regards, MartijnRe: FY26 incentive payout change
Hi Martijn, It appears there are >1 versions of the CSP accelerate FAQ where you found this snip. In a new and extended version there is also a Q & A below the one mentioned above. no partner (currently) impacted nor impact on how incentives are earned (yet) Same FAQ mentions new policies will go into effect after 1st of July "COCP patterns" as measured since that announcement will shape current policies which may impact incentive eligibility Luckily we will all be provided crystal clear guidance in advance to these changes going into effect. With a little over 5 weeks to go to 1st of July I expect details to be published soon! </happy path>
