Renewing EA vs. Switching to CSP: Deciding Your Microsoft Licensing Path
Executive Summary
When a Microsoft Enterprise Agreement comes up for renewal, enterprises face a crucial choice: renew the EA for another term or switch to a Cloud Solution Provider (CSP) model (or other licensing program).
This article helps CIOs, CTOs, and procurement heads weigh the pros and cons of staying on an EA versus moving to a CSP. It discusses cost implications, flexibility, minimum requirements, and strategic considerations for 2025.
The goal is to guide decision-makers to the best licensing path for their organization’s needs rather than automatically renewing out of habit.
Enterprise Agreement vs. CSP
Before deciding, it’s important to grasp how these two licensing models differ:
- Enterprise Agreement (EA): An EA is a 3-year contract directly with Microsoft (often via a reseller) covering a broad set of Microsoft products for your whole organization. It typically requires a commitment to license all users or devices for certain core products (like Windows, Office, and CALs). It has a minimum of 500 users/devices (with larger tiers offering bigger discounts). You lock in pricing for the term, pay annually (or upfront) for a set quantity of licenses, and can true-up for additional licenses yearly. Software Assurance (upgrade and support benefits) is included. In short, EAs favor standardization and give volume discounts in exchange for a firm, enterprise-wide commitment.
- Cloud Solution Provider (CSP): CSP is a subscription licensing program sold through Microsoft partners on a flexible basis. There’s no long-term contract – you generally pay month-to-month or annually per user, and you can increase or decrease licenses as needed. There is no minimum user requirement; you can license as few as five users or as many as 5,000. CSP covers most of the same Microsoft 365 services and Azure offerings, but pricing is set by the CSP partner (with Microsoft’s baseline). It often doesn’t include Software Assurance by default (since many CSP offerings are cloud subscriptions that are always updated). CSP is essentially pay-as-you-go, allowing for scaling up or down at will.
Key differences at a glance:
An EA locks you in for three years with fixed counts (high commitment, high discount), while CSP lets you stay agile (low commitment, lower or no discount beyond standard pricing).
EAs come directly (contracts with Microsoft), and CSP involves a partner who manages your licenses and billing.
Read Microsoft EA Renewal Timeline and Checklist for CIOs.
Evaluating Your Organization’s Needs and Scale
The right choice depends largely on your organization’s size, IT strategy, and how predictable your needs are:
- Organization Size & Stability: Generally, large enterprises (500+ seats, and especially thousands) get more value from an EA’s discounts. The more stable your user count is, the more an EA’s volume pricing will save money compared to CSP’s per-user rates. Conversely, smaller organizations or those with fewer than 500 users may find that they no longer qualify or benefit from an EA. Microsoft has been encouraging smaller clients to adopt CSP or the Microsoft Customer Agreement in recent years. CSP might align better if your headcount has dropped or fluctuated seasonally, as you haven’t been paying for a high-water mark for users for three years.
- License Flexibility: How often do you add or remove users or spin up/down services? Suppose you undergo frequent changes (e.g., a company with high turnover, many contract workers, or dynamic project-based use of cloud resources). In that case, CSP’s flexibility in adjusting licenses monthly can prevent the need to pay for idle licenses. On the other hand, if your IT needs are relatively steady and you prefer budgeting consistency, the EA’s fixed annual bill (with only occasional true-ups) means no surprise costs from month to month.
- Product Breadth: EAs are great for covering a wide swath of Microsoft products under one agreement – Windows, Office 365, EMS security suite, servers, Azure, etc., all consolidated. If your organization uses a broad Microsoft stack, an EA keeps it streamlined and often cheaper as a bundle. If you only use a few Microsoft services heavily (say just Microsoft 365 and a little Azure), you might manage fine with CSP subscriptions for those and not need the overhead of an EA.
- Budgeting and Cash Flow: EAs allow predictable budgeting. You know the bulk of your Microsoft spend for the next 3 years, which can appeal to CFOs. CSPs will have usage-based billing; monthly costs may vary if you add or drop licenses or consume more cloud services. Some finance teams prefer the EA’s stability, while others prefer CSP’s “pay only for what we use,” even if it’s variable. Consider which approach aligns with your financial planning style.
- Long-Term IT Strategy: If your company is going “all-in” with Microsoft long-term and values things like Software Assurance benefits (e.g., training vouchers, upgrade rights), an EA renewal cements that partnership and usually brings those perks. Suppose you foresee shifting away from Microsoft in some areas or adopting more third-party or open-source solutions. In that case, a shorter-term CSP model allows you to decrease Microsoft usage without being locked in or wasting part of a 3-year deal.
By evaluating these factors—size, flexibility needs, product range, budgeting approach, and strategy—you’ll have a clearer preference for sticking with an EA over switching to a CSP.
Benefits of Renewing Your EA
Why might you continue with an Enterprise Agreement? There are several advantages to consider:
- Volume Discounts = Lower Unit Costs: An EA’s pricing often beats what you’d get via CSP for large deployments. Microsoft rewards bigger commitments with tiered discounts. If you have thousands of seats, the per-user per-year cost under EA (especially after negotiation) could be significantly less than standard CSP rates. Over three years that can mean millions in savings for big companies.
- Included Software Assurance (SA): An EA bundles SA on many products. This gives you rights to new version upgrades, access to certain free training or support incidents, and, for some products, hybrid use rights. If you needed those benefits for Windows or SQL Server in CSP, you might have to pay extra or simply not have them. Enterprises that leverage SA heavily (e.g., regularly upgrading to the latest Office or using Azure Hybrid Benefit from SA) often prefer an EA.
- Contractual Commitment and Coverage: A single contract covering the whole enterprise can simplify license management and ensure compliance. You don’t have to juggle multiple renewal dates for different subscriptions; everything co-terms on the same schedule. It also provides a sense of “all-in partnership” with Microsoft, which can give you leverage to gain attention from Microsoft’s side (such as dedicated account management and faster support responses for large accounts, etc.).
- Predictability and Price Protection: When you renew an EA, you lock in the pricing for the term on the included products. This shields you from Microsoft’s public price hikes or currency fluctuations. For example, if Microsoft announces a 10% price increase for Office 365 next year, your EA pricing would typically remain as initially agreed upon. With CSP, prices could rise anytime, and you’d eventually pay the new rates once any subscription term ends.
- Eligible for Promotions/Programs: Microsoft sometimes offers enterprise-only incentives (like funding for deployments or promo discounts on bundle additions) that apply to EA customers. Also, certain large cloud commitment deals (like Azure consumption commitments) are easier to negotiate in an EA context. They can yield bonus credits or discounted rates not available in CSP’s pay-go model.
- Enterprise-Level Terms: EAs can include negotiated terms that a standard CSP agreement typically does not include. For instance, you might negotiate a custom clause in an EA that allows you to reduce some licenses mid-term if a divestiture occurs, or to swap a product for another of equivalent value. CSP agreements are more off-the-shelf, with little room for bespoke terms.
In summary, renewal is attractive if the cost-per-license is lower with EA, and you value the extras and assurances that come with a big Microsoft deal. Large, stable enterprises often stick with EAs for these reasons.
Benefits of Switching to CSP
Why do some organizations (especially mid-market or those with changing needs) move to CSP at renewal?
- Ultimate Flexibility: With CSP, you can increase or decrease licenses on a monthly basis. This means you only pay for what you need. If you downsize or have seasonal staff reductions, you immediately reduce your subscription count and costs – something impossible in an EA until renewal. That agility can prevent overspending on unused licenses in today’s environment, where business changes quickly.
- No Big Upfront Commitments: CSP does not force you to commit to enterprise-wide coverage. Perhaps you have 1,000 employees, but only 700 use a specific software – under EA, you might have had to license all 1,000. In CSP, you license 700, and that’s it. Additionally, there’s no 3-year locked term. While you may sign a 1-year CSP subscription for some services to receive a slight discount, you’re not similarly bound and can even switch providers or stop after a year if needed.
- Access to a Variety of Partners and Services: When buying through a CSP, you work with a Microsoft partner. Many partners bundle extra services – for example, they might include enhanced support, migration assistance, or a proprietary portal for managing licenses. If you choose a good CSP provider, they can act as an extension of your team for license management and optimization, sometimes more proactively than Microsoft directly would under an EA. You can also shop around at renewal time among CSPs to see who offers the best package (introducing a bit of competition that isn’t there with a single Microsoft EA).
- Easier to Start Small or Trial: If you’re considering new Microsoft products or services, CSP lets you pilot them with a handful of users without committing enterprise-wide. For example, if you’re curious about Microsoft Viva or a limited Power Platform use, you could start those with CSP subscriptions for just the interested teams, rather than having to amend your EA. This granularity can be cost-effective if not every new technology is suitable for organization-wide rollout.
- Potential for Cost Savings in Specific Scenarios: CSP might be less expensive if your organization is not large enough to qualify for deep EA discounts or if you anticipate a reduction in required licenses. For instance, a company that downsizes from 600 to 400 users might find renewing an EA (which requires 500 min and paying for 500+) wasteful, whereas with CSP, they’d pay exactly 400 after the downsizing. Additionally, CSP can facilitate the mixing of different license types per user more smoothly. While an EA tries to standardize, in CSP, you could have, say, 100 users on Microsoft 365 Business Premium, 200 on E3, 50 on E5, etc., if that fine-tuned mix fits better and possibly cheaper than an all-E3 or all-E5 approach in an EA.
The bottom line is that organizations that value flexibility, granularity, and the avoidance of lock-in lean toward CSP. It’s especially popular with smaller and heavily cloud-focused enterprises that have transitioned away from Microsoft’s on-premises products.
Microsoft’s Push Toward CSP and New Agreements
It’s worth noting that Microsoft’s licensing landscape is evolving.
In 2025, Microsoft has been encouraging a shift away from traditional EAs in some cases:
- Raising EA Minimums: There have been indications that Microsoft is effectively raising the bar for who can have an EA, steering sub-500-seat customers to CSP or the Microsoft Customer Agreement (MCA). The MCA is an agreement primarily for Azure and online services with no minimum, often used by mid-sized firms and those buying via Microsoft’s web portal. If your user count has dropped below Microsoft’s thresholds, you might find Microsoft itself less inclined to offer an EA renewal, pointing you to CSP/MCA instead.
- Cloud-Only Organizations: If you no longer use on-premises licenses and are 100% cloud-based (Office 365, Azure, Dynamics Online), Microsoft sometimes suggests an MCA-based approach for direct cloud consumption or a CSP for user subscriptions, as the EA was traditionally more hybrid. They’ve not allowed pure-cloud small deals to be EAs in certain regions. So, your product mix could influence the path.
- Incentives to Move: Microsoft and partners occasionally provide incentive discounts or offers for moving from EA to CSP. For example, a partner might offer a 5% rebate on first-year CSP costs to woo an EA customer, or Microsoft might extend a one-time discount on Azure if you switch to the new commerce platform. Keep an eye out – if you’re considering a switch, these incentives can ease the transition cost.
- MCA-E (Enterprise): Microsoft has introduced the concept of an MCA for enterprises, a more flexible, evergreen contract for large customers, with a focus on Azure. It’s not exactly CSP, but it shows Microsoft’s trend toward more cloud subscription models, even for big clients. In some renewal cases, Microsoft may propose an MCA for Azure, combined with CSP for Microsoft 365, instead of a legacy EA. This hybrid model might suit some, but be aware that it’s a relatively new approach.
Knowing Microsoft’s direction, if you feel they are less invested in the EA model for your segment, that’s a sign to evaluate alternatives.
The worst outcome would be to renew an EA that becomes stale mid-term if Microsoft changes programs, but being an early adopter of a new model has its risks (tools and processes may not be as smooth initially).
Weigh the momentum: you don’t have to switch if EA still serves you well, but be aware of external pressure and plan accordingly.
Considering a Hybrid Approach
Your decision need not be all-or-nothing. Many enterprises find a middle ground to maximize benefits:
- EA for Core, CSP for Fluctuations: One strategy is to renew a smaller EA that covers your stable core (perhaps just Office 365 for all employees at a volume-discounted rate, plus a base of Windows/EMS for devices you know you’ll have). Then, use CSP for anything uncertain or growing. For example, you could exclude Azure from the EA and consume it via a partner under CSP/MCA, where you can scale resources up or down freely. Alternatively, if you’re unsure about certain user counts, consider keeping a portion of users on EA and any additional users on CSP with short-term commitments. This hybrid licensing can save costs by not over-committing on the variable parts of your usage.
- Transition Over Time: Some companies make a phased move. They renew the EA one last time, but maybe for a shorter term or with fewer products, with the plan that by the end of that period, they’ll be ready to switch fully to CSP/MCA. This gradually gives time to adjust internal processes (like budgeting monthly costs, managing through a partner portal, etc.). If you’re culturally or operationally very used to EA management, a gradual transition can mitigate disruption.
- Mixing Licensing Programs by Product: It’s perfectly acceptable (in Microsoft’s eyes) to have your Microsoft 365 licenses under an EA while buying Azure via an MCA. Or using EA for on-premise Windows/Office and CSP for certain cloud subscriptions. Each program has its strengths; align them with what they’re best suited for. Just be cautious to keep track of it all – you’ll have multiple agreements to manage and renew if they come up at different times.
A hybrid approach can deliver a “best of both worlds” outcome, but careful governance will ensure nothing falls through the cracks (e.g., not double-buying the same product in two channels or missing a CSP renewal since it’s annual).
Recommendations
- Assess your usage stability. If your user count and product needs are steady and large, an EA likely provides cost advantages. If they fluctuate or you’re downsizing, lean towards CSP for flexibility and savings on unused licenses.
- Calculate the 3-year total costs under each scenario. Include license costs, support, and any benefits lost/gained (like training days or upgrade rights). Sometimes CSP looks cheaper monthly but could be higher over 3 years versus a discounted EA, or vice versa. A detailed cost projection will make the choice clearer.
- Check Microsoft’s thresholds and guidance. If you’re below 500 seats (or whatever current EA minimums are), Microsoft might not even offer a traditional EA. Don’t fight uphill – consider programs tailored to your size. If you’re above that, use your volume as leverage in an EA renewal negotiation.
- Consider partial moves. It’s not an all-or-nothing decision. You can renew an EA for the pieces that make sense and move other portfolio parts to CSP or MCA. Align each licensing model with the needs of the specific product or user group (e.g., a stable workforce on EA, contingent workers on CSP).
- Engage a trusted Microsoft partner. If leaning toward CSP, evaluate different CSP providers. A good partner might offer better customer service, proprietary cost management tools, or bundle consulting hours – the value you won’t get in a direct EA. Partners can quote CSP pricing for comparison leverage, even if you stay with EA.
- Think about contract flexibility. If you renew an EA, negotiate terms that provide some indication of whether things will change (e.g., the ability to reduce if you divest a business unit). If you go CSP, ensure you’re not signing overly long commitments with a partner that negates the flexibility.
- Don’t forget compliance. Switching to a new licensing model can introduce additional compliance considerations. For example, perpetual licenses from an EA might need careful handling if you drop SA. Ensure that any transition doesn’t accidentally put you out of compliance. Microsoft’s rules differ slightly between programs – have licensing experts double-check your plan.
- Plan the administrative impact. EA renewals involve true-ups and significant renegotiations every few years. CSP is a more continuous management approach (monthly adds and removals). Ensure your team and processes are prepared for the model you select. CSP may require regular oversight, whereas EA involves more periodic heavy lifting.
- Stay informed on Microsoft’s roadmap. Licensing models evolve. Keep an eye on announcements—for instance, if Microsoft were to offer EA-like discounts through CSP for specific products or if new product bundles become available. Being aware of these can influence your decision.
- Prioritize what the business values. EA’s fixed nature might win if your CFO values predictable spending over the lowest cost. CSP’s flexibility is key if your CEO wants maximum agility to pivot resources. Weigh the licensing choice not just on IT factors but also on what aligns with business priorities.
FAQ
Q1: Is there a minimum size or seat count for an Enterprise Agreement vs. CSP?
A: Yes. Microsoft Enterprise Agreements traditionally require at least 500 “qualified users or devices” to enroll (with some exceptions like public sector or academic agreements). Microsoft has been raising the bar for new EAs, often targeting 2,400+ users for the best discounts. If you fall below the minimum, you wouldn’t officially qualify for an EA renewal unless you are grandfathered; in this case, Microsoft would direct you to other programs, such as CSP or Open Value. Conversely, CSP has no minimum – you could have just one user, though it’s typically used when you don’t meet the EA scale or need flexibility. CSP becomes the default choice if your organization has shrunk below EA eligibility.
Q2: Can we partially renew our EA and move some products to CSP?
A: Absolutely. When your EA expires, you can renew only certain product components under a new EA, allowing other components to lapse and be replaced with CSP subscriptions. For example, you might renew the EA for Windows OS and Office 365 but not include Dynamics 365 because you plan to use CSP for Dynamics licenses. It requires planning – coordinate the end of the EA coverage for the dropped products with the start of CSP so there’s no gap. Microsoft may require you to sign an EA amendment listing the products that are renewed. This hybrid approach can be somewhat complex administratively, but it’s permitted. Ensure you maintain compliance during the switch (don’t double count or leave anyone unlicensed).
Q3: Which is cheaper: EA or CSP?
A: There’s no one-size-fits-all answer; it depends on your volume and usage pattern. For a large, steady state (i.e., 1000+ users consistently using Microsoft 365 E3), an EA will usually be cheaper per user due to volume discounts. For a smaller or very volatile usage (say 300 users, that might drop to 250 in a year), CSP could be cheaper overall because you’re not over-buying and you’re not paying for unused licenses. It’s also about product mix: if you need Software Assurance or on-prem licenses, an EA can package that more economically. We recommend calculating a comparison: take your current license counts and apply your EA pricing (with any anticipated discount) vs. the CSP partner’s quote for the equivalent. Also, consider the 3-year total cost of EA (since you’re committing) vs. the CSP’s ability to reduce spending if your needs decline.
Q4: If we switch to CSP, do we lose Software Assurance benefits like upgrades or training vouchers?
A: In many cases, yes – at least in the way they exist under EA. CSP for cloud services (such as Microsoft 365 and Dynamics Online) inherently provides access to the latest versions, as these services are subscription-based. But for traditional on-prem licenses, CSP doesn’t include SA; you’d be buying, for example, perpetual licenses without SA or subscribing to software differently. Some SA benefits, such as training days or planning services, are not available through CSP. Additionally, if you previously received benefits such as home use rights for Office or long-term support for Windows, these may change. However, Microsoft has been shifting some benefits to be available via cloud subscriptions (e.g., Microsoft 365 subscriptions include most of what SA did). It’s worth mapping out each benefit: e.g. if you relied on license mobility to the cloud (an SA benefit) for SQL Server, moving to CSP licenses might require a different approach. Ensure no critical SA benefit is lost, or if it is, that you can live without it or replace it (sometimes you can purchase SA separately for certain licenses even outside an EA, but it complicates things).
Q5: How do support and billing work differently with CSP vs. EA?
A: With an EA, you usually have a direct billing relationship with Microsoft (though often invoiced through an LSP – licensing solution partner – but essentially, it’s a Microsoft agreement). You can purchase product support separately (Premier/Unified) or utilize what’s included in SA. With CSP, your partner often handles Tier-1 support and billing. You’ll receive bills from the CSP partner (monthly or annually) for your subscriptions. Many CSP partners offer basic support as part of their service (like help with provisioning or issues) and escalate to Microsoft if needed. You might not need a separate Microsoft support contract for cloud services if the partner covers it, but for complex issues, you may still rely on Microsoft’s higher-tier support. It’s important to clarify with a potential CSP provider: What support do they include? Some include managed services or dedicated reps. Billing-wise, CSP can also provide more detailed usage breakdowns since they bill monthly, which can help with showback or chargeback internally if you allocate IT costs.
Q6: We’re mid-sized now but plan to grow significantly in the next two years. Should we go EA or CSP?
A: If significant growth is expected (and relatively certain), an EA could be beneficial to lock in pricing now for future higher quantities. For example, you currently have 400 users (CSP might seem fine), but plan to expand to 800 in 2 years. An EA would perhaps secure volume pricing at the 800 level, and you’d just true-up gradually. Microsoft might even give you a discount, anticipating that growth. If you stay on CSP, your costs will double when your user base doubles (assuming per-user pricing remains the same). However, consider the nature of growth: if it’s through acquisition, different units may have different IT setups – flexibility could be a key factor. An EA can be a strategic financial win if it’s organic and you’re sure to remain a Microsoft shop. One approach is to start with CSP for a year to see how growth trends unfold, then transition to EA when you reach the threshold where EA becomes sensible. Keep communicating with Microsoft – they’ll likely be happy to move you onto an EA when you get large enough and might offer incentives then.
Q7: Can we switch from an EA to a CSP before the EA term ends?
A: Typically, no – you are contractually committed to the EA for its full 3-year term (unless you terminate early, which is usually not feasible without still paying for the full term). The usual time to switch is at the renewal point. If they want to shift gradually, some reduce the EA to a minimum at renewal and then later refuse to renew. But in the mid-term of an EA, you cannot just stop and move to CSP without still being on the hook for the EA payments. You can add CSP subscriptions even while your EA is active (for new needs not covered by the EA), but you’d be paying extra rather than substituting. So, plan your strategy for the end of the EA term. Mark that expiration date and align any CSP transitions to start right after. If you had to end the EA early (e.g., the company split up), you’d have to negotiate with Microsoft – that scenario is complex, and Microsoft might impose penalties or require you to pay out the agreement.
Q8: What is the Microsoft Customer Agreement (MCA), and how does it relate to EA vs CSP?
A: The Microsoft Customer Agreement is a newer contract framework primarily used for Azure and other Microsoft online services. It’s “evergreen” (i.e., it has no end date and can be terminated with notice) rather than a fixed-term contract. It’s sort of Microsoft’s move to modernize enterprise purchasing. Think of it as pay-as-you-go, like CSP, but directly with Microsoft. For Azure, many enterprise customers are transitioning from EA to MCA because Microsoft aims to drive cloud consumption on the new commerce platform. MCA is less common for Office 365 and other per-user subscriptions (those often still go through CSP). You might encounter MCA if Microsoft says, “Instead of renewing Azure in your EA, we’ll put you on an MCA for Azure.” The differences between MCA and CSP are subtle (CSP is facilitated through a partner, whereas MCA is direct). Both offer flexibility. Therefore, if you are considering leaving EA, you can either go CSP through a partner or sign an MCA and purchase directly. Each has pros/cons. CSP could come with partner support, and MCA might offer direct billing with Microsoft, providing better insight into significant Azure spending. For many organizations in 2025, the decision isn’t just whether to use EA or not, but also which non-EA route to choose: CSP or MCA. Evaluate based on whether you want a partner’s help and whether you’re mostly consuming Azure (MCA makes sense there) or user licenses (CSP is common there).
Q9: If we choose CSP, what happens to our existing data and setup in Microsoft 365/Azure?
A: In most cases, nothing disruptive – CSP is just a different licensing vehicle. You wouldn’t have to migrate data; it’s an administrative change. For example, say you had an EA that covered Office 365 E3 for your users. At the end of EA, you decide to go CSP. Your CSP partner would reassign those licenses to your tenant under their provider account. Users retain the same accounts, mailboxes, etc. It’s essential to plan the timing: ideally, have the CSP licenses provisioned the day after your EA expires, ensuring no lapse. Microsoft has processes in place to smoothly transition customers from EA to CSP (partners often do this). For Azure, you’d transition subscriptions to the new agreement (there are methods to transfer an Azure subscription from EA enrollment to an MCA/CSP enrollment). It should be largely transparent to end-users. Coordinate closely with the partner and Microsoft to ensure a seamless transition of the licensing context to the backend. Also, ensure you purchase equivalent or greater licenses in CSP so that no user goes unlicensed during the cutover.
Q10: Could we leave Microsoft licensing at renewal (switch to other vendors)?
A: This broader question arises during EA renewal discussions as leverage. Some organizations consider migrating to Google Workspace, AWS, or other platforms instead of renewing their Microsoft agreements. If that’s genuinely on the table, a CSP vs EA debate might be moot because you’re evaluating leaving the Microsoft ecosystem partly or wholly. If, for instance, you’re unhappy with Microsoft’s costs, you might compare the cost and feasibility of Google’s offering for email/collaboration or Amazon for cloud infrastructure. However, such moves are large undertakings and are usually not solely driven by licensing convenience. Most enterprises stick with Microsoft and optimize their operations within its programs. However, you can use the possibility as a negotiation point (“We might reduce our Microsoft footprint and not renew product X”) to see if Microsoft offers a better deal. If you truly plan to exit certain Microsoft products, consider shorter commitments (such as CSP’s month-to-month) for the remaining time to maintain flexibility. Always ensure you have the alternative ready – don’t bluff too hard without preparation, or you might end up unlicensed. But yes, theoretically, renewal time is when you could pivot to other solutions entirely if they better meet your needs.
Read about our Microsoft EA Negotiation Service.
