- 1. What is Microsoft Marketplace?
- 2. How does it support an organization's confidence?
- 3. Marketplace validation and certifications: what each means
- 4. Security and shared responsibility
- 5. Privacy, data residency, and processing
- 6. International availability and purchasing requirements
- 7. How to purchase and activate Legale CLM
- 8. Pricing, licensing, and commercial scope
- 9. Who issues invoices, and when?
- 10. Local invoicing, currency, and taxes
- 11. Spending control and Azure consumption commitments
- 12. Renewals, changes, and cancellations
- 13. Support and documentation for your assessment
- 14. Frequently asked questions
A guide for procurement, finance, technology, security, and legal teams. Legale CLM’s presence in Microsoft Azure Marketplace allows organizations to evaluate our contract lifecycle management solution within Microsoft’s commercial ecosystem. This guide explains how that channel works, how it supports business confidence, and what your organization should review before subscribing.
For information about Legale’s current offer, supported countries, plans, and terms applicable to your business, ask our team for guidance. The offer listing and the terms accepted during purchase determine the scope of each subscription.
1. What is Microsoft Marketplace? #
Microsoft Marketplace is the commercial catalog of solutions from Microsoft and its partners. It helps customers discover business software, review provider information, and explore purchasing options. Azure Marketplace is the name many customers use for the solutions experience available through Azure.
With a SaaS—software as a service—solution, customers use an application managed by its provider. The purchasing channel facilitates the subscription, while configuration, implementation, and application use follow the provider’s process. Some offers allow direct purchases; others offer a trial or a contact request. The button and plan available in the listing indicate the appropriate path. See Microsoft’s SaaS offer options.
2. How does it support an organization’s confidence? #
Marketplace can help structure evaluation and procurement by providing an identifiable product listing, commercial information, and links to terms, privacy information, and support. For organizations already working with Microsoft, it can also help procurement and finance teams incorporate third-party software into their existing processes.
Confidence comes from combining three elements: reviewing the purchasing channel, examining the provider’s evidence, and assessing the customer’s chosen configuration. We recommend keeping the version of the offer purchased, the plan identifier, the accepted terms, and a record of those responsible for the purchase. This supports the decision with verifiable information that can be reviewed during an internal audit.
3. Marketplace validation and certifications: what each means #
Microsoft sets publishing and certification policies for Marketplace offers. The applicable requirements depend on the solution type and cover aspects of the listing, commercial terms, and technical operation of the offer. Transactable SaaS offers have additional requirements for integration with the purchasing process. See the official publishing and certification policies.
Approval to publish an offer does not, by itself, constitute ISO certification, a SOC 2 report, or a guarantee that the solution has no vulnerabilities. References to being “validated by Microsoft” should be understood within the scope of the Marketplace process applicable to the offer.
To assess Legale’s certifications and controls, visit our Trust Center and request the current evidence your organization needs. We recommend checking:
- The legal entity and service covered by each document.
- The scope: processes, systems, locations, and exclusions.
- The issue date, validity, or assessment period.
- The organization or auditor that issued the evidence.
- The controls relevant to your intended use of Legale and the customer’s responsibilities.
A logo or membership should be accompanied by information about its scope. For a formal assessment, use the corresponding documents rather than relying solely on marketing materials.
4. Security and shared responsibility #
In the cloud, security requires coordinated responsibilities. Infrastructure, the application, and user administration form different layers. Customers retain responsibilities for their data, identities, and the components they control. Microsoft describes this principle in its shared responsibility model.
When implementing Legale, agree on a responsibility matrix with our team covering the following:
- Access: administrators, roles, least privilege, and user onboarding, changes, and offboarding.
- Identity: authentication methods, single sign-on compatibility, and multifactor authentication requirements for your environment.
- Information protection: applicable encryption controls, access management, and handling of sensitive documents.
- Traceability: available events, permissions to view logs, and retention or export requirements.
- Vulnerabilities and incidents: reporting channels, escalation procedures, and available review evidence.
- Continuity: backups, recovery, agreed objectives, and service scope.
This list is an assessment framework; included capabilities must be confirmed for the purchased plan and configuration. You can start with our Security Policy and Service Level Agreement (SLA).
5. Privacy, data residency, and processing #
The country where a purchase is made, the invoicing entity, and the location where data is processed are separate matters. For contracts containing personal or confidential information, we recommend documenting the following before implementation:
- The categories of data to be uploaded and their intended purpose.
- The entity providing the service and the applicable processing agreements.
- The storage and processing locations applicable to the service.
- The subprocessors and international transfers that need to be assessed.
- The retention, export, and deletion timelines when the relationship ends.
- The procedure for handling requests concerning personal data.
Review the Privacy Policy and the documentation on personal data protection at Legale. Ask our team for the details required for your industry, country, and type of information.
6. International availability and purchasing requirements #
Availability must be checked for the offer, plan, and billing country of the subscription you intend to use. Some options may be restricted to specific markets or tenants. Presence in a global catalog does not mean that every plan is available in every country.
To purchase a SaaS offer through Azure, you need an account with access to a suitable subscription and Marketplace purchasing permissions. If your organization restricts purchases or resource creation, coordinate approval with your administrator first. See the SaaS purchasing requirements and process.
7. How to purchase and activate Legale CLM #
- Define the scope. Tell our team about your users, contract processes, integrations, countries, and implementation needs.
- Confirm the offer. Request access to the current listing or proposal and check the provider name and plan.
- Review the subscription terms. Validate the duration, price, billing frequency, renewal, terms of use, and privacy provisions.
- Complete the authorized purchase. Use the account and subscription approved by your organization.
- Configure the service. Follow the activation instructions and complete onboarding with Legale.
- Record the responsible contacts. Designate administration, security, finance, and support contacts.
Automatic activation or subsequent configuration depends on the plan. Check the billing start time shown during purchase. Purchasing the subscription and completing setup are steps that need to be coordinated. The SaaS subscription management guide explains the operations available according to the subscription status and purchasing channel.
8. Pricing, licensing, and commercial scope #
Before approving the budget, request a proposal that separates the recurring service from implementation and any additional services. Check whether the plan includes a fixed fee, per-user licenses, or variable components, and which limits apply. Do not assume that all these models are available for Legale: they must appear in the current offer.
It is advisable to document the number of users, included modules, integrations, training, support, and treatment of additional usage. Distinguish the commitment term from the payment frequency: paying monthly does not necessarily mean subscribing for one month. If you need negotiated terms, ask whether a private offer is available for your organization.
9. Who issues invoices, and when? #
For purchases transacted through Microsoft, how charges are presented depends on the account and billing agreement. EA and MCA accounts may consolidate Azure and Marketplace charges, with exceptions by country and product; MOSP accounts receive a separate Marketplace invoice. Certain products for MCA customers generate an invoice within 24 hours of purchase, while metered components may follow a monthly cycle.
Confirm the schedule shown in the transaction and who can download invoices. The arrangement is not identical for every business. See the official Microsoft Marketplace billing guide.
10. Local invoicing, currency, and taxes #
Tax handling depends on the country and commercial model. Microsoft distinguishes Microsoft-managed, publisher-managed, and reseller jurisdictions, with different tax responsibilities. When a CSP or LSP provider is involved, the billing relationship with the end customer also changes. See the official Marketplace tax information.
“Local invoicing” must be confirmed for the purchasing entity and chosen channel. Before paying, ask your finance team to validate the legal business name, tax identifier, address, currency, invoice issuer, and applicable taxes. If you need a country-specific tax document, check that the channel can issue it and which details it requires. The transaction documentation determines these conditions.
11. Spending control and Azure consumption commitments #
We recommend assigning a budget owner, keeping the purchase order reference, and reconciling charges against the purchased plan. Where variable components exist, agree on how usage will be reviewed and when capacity changes should be requested.
Some eligible purchases contribute toward a Microsoft Azure Consumption Commitment (MACC). The program requirements must be met, including the Azure benefit eligible designation and purchase through the Azure portal using a subscription linked to the agreement. This does not mean that any Azure credit can be used to pay for third-party software. Confirm Legale’s specific eligibility before including this benefit in your budget. See the MACC benefit terms.
12. Renewals, changes, and cancellations #
Review the expiration date, automatic renewal, and subscription management permissions. Changes to plans, users, or renewal depend on the product and subscription status. Maintain an internal calendar to assess continuation in advance, and consult the SaaS lifecycle management documentation.
Microsoft’s general SaaS policy provides for a refund when cancellation occurs within 72 hours of purchase, excluding metered charges. After that period, a request requires contacting the publisher and obtaining its approval for processing. Free trials have their own terms. Always review the current refund policy and the details of your transaction.
Before closing the service, coordinate information exports, access, and data handling with Legale. Turning off renewal, canceling a subscription, and completing the exit from the platform require joint planning.
13. Support and documentation for your assessment #
For questions about Legale’s features, implementation, or terms, use our support channel or request guidance through onboarding. For issues with a purchase or invoice managed by Microsoft, identify the billing account and use the appropriate channel’s support.
To speed up assistance, have the offer name, plan, purchase date, and subscription identifier available. Share only the necessary information and avoid including sensitive contracts in a commercial inquiry.
Your assessment file can include the proposal, terms and conditions, privacy policy, SLA, and evidence available in the Trust Center.
14. Frequently asked questions #
Does Microsoft become the provider of Legale CLM? #
Legale remains the solution your organization uses. Identify the contracting parties, service provider, and entity managing payment in the offer. The commercial channel and application support perform different roles.
Does publication demonstrate all security certifications? #
The Marketplace assessment has its own scope. For your business’s security requirements, review the service-specific evidence and its validity in the Trust Center.
Can I obtain a valid invoice for my business? #
Confirm the country, tax details, and available document with the purchasing channel before completing the transaction. Our team can help you identify which information needs to be validated.
Are implementation, integrations, and training included? #
This depends on the purchased proposal. Request a breakdown of deliverables, responsibilities, timelines, and additional services to plan adoption.
Where will my contracts be stored? #
Request the location and processing terms applicable to your service. The market where you purchase or receive an invoice does not, by itself, determine data residency.
How do I get started? #
Request guidance on purchasing Legale CLM through Marketplace. Provide your business’s country, estimated number of users, and procurement, security, and billing requirements so we can prepare the appropriate path.
Informational guide reviewed on September 7, 2026. The linked official sources and offer terms allow you to check the requirements in effect at the time of purchase.
AI