Postclic premium unlimited: promotional offer at RM 4.19 for 48h, then RM 228.34 per month without commitment

Cancellation service #1 in Malaysia
Microsoft Azure is Microsoft’s cloud platform, launched in 2010 and operated by Microsoft Corporation, whose main headquarters is in Redmond, Washington. In simple terms, Azure lets companies and individual developers rent computing power, storage, databases, networking, security tools, and developer services instead of buying and running everything on their own servers.
For Malaysian users, the confusing part is that Azure is not one simple flat subscription like a video streaming app. A lot of Azure billing is usage-based, so charges can continue if a virtual machine, SQL database, storage account, or support plan is still active. That is why many users feel annoyed after trying to cancel, especially when the portal is not very senang to navigate.
Most people are paying for one of two things on Azure. The bigger part is cloud resources such as virtual machines, storage, managed databases, backup, analytics, and networking. The second part can be a recurring support plan, such as the Developer plan at $29.00 (RM137)* per month, listed by the pricing data provided.
This matters for cancellation because stopping a support plan is not always the same as deleting billable resources. A user may cancel one service but still get billed for a database, storage, or reserved capacity. One negative review in the research data described charges continuing after services were deleted, which shows why you must check every active resource before you hit cancel.
In Malaysia, Azure is available for business and individual use, and Microsoft account management is done online through the Microsoft account and Azure portal. The verified refund policy says Malaysia does not get prorated refunds for unused time on Microsoft subscriptions, so timing matters a lot if you want to stop future charges without expecting money back for the leftover period "support.microsoft.com".
Azure pricing in Malaysia is not neatly published in MYR across every service in the supplied source set. The official pricing page explains a pay-as-you-go model and commitment options such as Reservations and Savings Plan for Compute "azure.microsoft.com". So if you signed up quickly, you may actually have agreed to a mix of monthly support billing and metered cloud usage, not one simple all-in package.
Many Microsoft Azure users get frustrated because the cancellation button is only one part of the job. Before cancelling, save any data you still need, note your next billing date, and capture screenshots of your current subscription page, active resources, and recent invoices. This helps a lot if a charge appears later.
Local complaint patterns in the research data say users struggle with portal navigation and find the process time-consuming. So do a quick audit before cancellation. Look for active virtual machines, SQL databases, storage accounts, backup vaults, support plans, and reservations. If any of these remain active, billing can continue even if you thought the account was already closed.
The verified Microsoft method is straightforward on paper. Sign in to your Microsoft account, go to Services & subscriptions, choose the subscription you want to stop, click Manage, then click Cancel subscription "learn.microsoft.com". If your goal is to stop future renewal, do this before the next billing date, not on the same day if you can avoid it.
If the portal feels messy, open the official Microsoft cancellation help page and follow it side by side. Use this support guide: Azure subscription cancellation guide. After clicking cancel, take a screenshot of the confirmation page and save any confirmation email. Without proof, disputes become much more leceh.
The research data does not provide a public phone number, support email, or support hours for Azure cancellation in Malaysia. It does confirm that support options are available through the Azure portal, and live chat is not specifically listed. So the practical route is to start inside the portal, open billing or subscription support, and keep every case number you receive.
If you want an extra paper trail, you can also send a written cancellation notice by registered mail to Microsoft’s Malaysia office. Some consumers prefer this when there is a billing dispute. A digital certified letter service such as Postclic can also create timestamped proof of sending, receipt, and opening if you want a modern record without queueing at the post office.
If you use written notice, keep it short and include your Microsoft account email, subscription name, billing reference, and requested cancellation date. This is not the main cancellation path, but it can support a refund dispute or KPDN complaint later if Microsoft does not respond clearly.
You can send the notice here:
After sending, keep the mailing receipt, tracking result, and a copy of the letter. Attach the same documents if you escalate the case to TTPM.
The practical result of cancellation is that future charges to continue the service should stop, according to the Microsoft policy wording on cancellation rights "support.microsoft.com". In real use, that usually means the subscription will not renew for another paid cycle. If you cancel close to renewal, check the final invoice because Malaysia does not get prorated refunds for unused periods.
If you have a one-month subscription, the supplied terms data says you may terminate at any time without a cancellation fee. If you have a longer commitment, the terms are harsher. Within the first 30 days, no refund is provided and you still pay for the initial 30 days. After 30 days, you must pay for the rest of the term "azure.microsoft.com".
The supplied terms say the agreement remains in effect until expiration, termination, or renewal, whichever comes first "azure.microsoft.com". That means if you do not cancel in time, the subscription relationship can continue into the next cycle or the rest of the commitment period. For users with active Azure resources, charges can also continue on a pay-as-you-go basis while resources remain running.
This is where many users trip up. They assume deleting one app or one database is enough, but Azure billing can involve separate billable components. If you want a clean exit, verify both the subscription status and the resource list on the same day.
The available source set does not clearly state a detailed Azure data retention timeline after cancellation. So do not assume your data will stay there safely or disappear neatly on a predictable date. Export what you need before cancelling, especially databases, storage blobs, VM snapshots, logs, and billing reports.
If you run workloads for a client or employer, tell them before deletion. A cancellation done too early can break apps, websites, backups, or development pipelines on the same day. Save data first, cancel second. That order matters.
This is the part many users dislike, but the rule is clear in the verified Microsoft refund policy. In Malaysia, prorated refunds are not available for Microsoft subscriptions, and there is no refund for the unused portion after cancellation "support.microsoft.com". So if you cancel halfway through a paid period, you should not expect half your money back.
The same policy says refund eligibility depends on timing, subscription type, and country of purchase. For billing errors, Microsoft says refunds are assessed case by case "support.microsoft.com". In practical terms, normal voluntary cancellation usually stops future billing only. A billing mistake has a better chance than a simple change of mind.
If the problem is a duplicate charge, post-cancellation billing, or a charge for a deleted resource, go through Microsoft support from the Azure portal and attach hard evidence. Include invoice numbers, transaction dates, exact amounts, screenshots of the cancelled subscription, and screenshots showing the resource was deleted. The more specific your file, the faster support can understand what went wrong.
The best wording is direct. Say the subscription was cancelled on a named date, the resource was deleted on a named date, and the charge appeared on a named invoice. Ask for an investigation and refund of the disputed amount. Keep the support case ID and wait for a written response.
If Microsoft ignores the issue or rejects a clearly unauthorised recurring charge, Malaysian cardholders can ask their bank for a chargeback or dispute a recurring card transaction. The timeline is commonly around 60 to 120 days from the transaction date or from when you discovered the issue, based on bank and card-network rules under Bank Negara Malaysia’s consumer protection framework and the Financial Services Act 2013 or Islamic Financial Services Act 2013.
Do this only after trying Microsoft support first, because your bank will usually ask for proof that you attempted to resolve the matter. Submit screenshots, invoices, support replies, and cancellation proof. If you paid through a card, the issuing bank is your key contact. If a different payment route was used, follow that provider’s formal dispute process.
The supplied Azure subscription agreement data gives one key point very clearly. For one-month subscriptions, you may terminate at any time without a cancellation fee. For subscriptions longer than one month, terminating within 30 days gives no refund and you still pay for the initial 30 days. After 30 days, you must pay for the remainder of the term, with no refunds provided "azure.microsoft.com".
This is the clause that catches people who assume cloud subscriptions behave like flexible month-to-month apps. If you accepted a longer commitment, cancellation does not mean escaping the rest of the term. It only ends what can be ended under that agreement.
The supplied terms data says the agreement remains in effect until expiration, termination, or renewal, whichever is earliest "azure.microsoft.com". The same data does not clearly detail a free trial conversion rule for Azure in the available source set. If you started on a promotional or limited offer, you should inspect your account billing page and any sign-up email because the source set does not fill in that missing detail.
The agreement is stated as governed by the laws of the United States in the supplied terms summary "azure.microsoft.com". For a Malaysian consumer, that does not remove your ability to complain locally about unfair charges or poor complaint handling. It simply means Microsoft’s own service agreement points to US governing law, while your payment dispute and consumer complaint options in Malaysia still matter in practice.
Plan | Price (USD / MYR) | Period |
|---|---|---|
Developer | $29.00 (RM137)* | Monthly |
Prices are approximate, converted from USD at the rate 1 USD ≈ 4.72 MYR. Check the official Azure pricing page for exact local prices.
The single recurring plan in the supplied verified data is the Developer support plan at $29.00 (RM137)* per month. Beyond that, Azure mainly uses pay-as-you-go billing for computing, storage, networking, databases, and other services "azure.microsoft.com". That means your real monthly spend may be far higher than the support plan if resources stay active.
Azure also offers commitment-based pricing such as Reservations and Savings Plan for Compute "azure.microsoft.com". Those can lower costs for steady workloads, but they also make cancellation less flexible. If your bill feels too high, the real issue may be active resources or commitment purchases, not only the support subscription itself.
Based on the limited verified recurring plan data, the Developer support plan is the only named subscription plan available here, so it is both the least expensive and the most expensive plan in this data set. The bigger pricing risk on Azure comes from metered usage. A forgotten SQL database, virtual machine, or storage account can cost more than the support plan over time.
For a Malaysian freelancer or SME, Azure can be good value if workloads are controlled closely. If you only needed a short test environment and forgot to shut it down, it can feel mahal very fast. Review invoices line by line before assuming the support plan is the only cost.
In Malaysia, consumer cancellation issues generally sit under the Consumer Protection Act 1999. But there is no universal cooling-off period for all online subscriptions. The 10 working day cooling-off right mentioned in the supplied jurisdiction block applies to direct sales under the Direct Sales and Anti-Pyramid Scheme Act 1993, such as certain door-to-door or direct sale contracts, not automatically to every online software service.
For Microsoft Azure, that means you usually cannot rely on a general Malaysian cooling-off right just because you changed your mind. This lines up with the Microsoft refund position that in Malaysia you are not entitled to a cooling-off period or refund in the ordinary sense "support.microsoft.com". So your strongest cases are billing errors, unclear charges, or failure to stop recurring billing after proper cancellation.
If Microsoft does not resolve a billing problem, start with KPDN because it handles consumer affairs and complaint channels in Malaysia. Prepare a short chronology with dates, the disputed amount in RM, screenshots, invoices, support case numbers, and proof of cancellation. If money is still in dispute after that, TTPM can be relevant for a consumer claim.
TTPM is the Tribunal for Consumer Claims Malaysia, a practical route for smaller consumer disputes without the full cost of a court case. Your evidence matters more than long arguments. Show the cancellation date, the invoice date, and the charge amount. If a post-cancellation charge appears, that timeline is your strongest point.
KPDN is the Ministry of Domestic Trade and Cost of Living, and TTPM operates under the consumer claims system in Malaysia. The jurisdiction data also names MCMC in the research block, but for subscription billing and consumer complaint handling, KPDN and TTPM are the more practical names to remember for most Azure users.
Based on the supplied review set, cancellation looks difficult rather than smooth. The review summary shows 0 positive and 1 negative unique review, with the main issue being charges after cancellation. The local issue data matches that pattern too, saying users struggle with subscription management in the portal and find cancellation complex and time-consuming.
That said, one review is still a very small sample. So the fair conclusion is this: the cancellation path exists and Microsoft documents it, but the practical risk is incomplete shutdown of billable resources and poor clarity around what is still charging.
Theme | Frequency | Typical example |
|---|---|---|
Charge after cancel | High | Deleted service still billed |
Portal confusion | High | Hard to find controls |
Slow resolution | Medium | Support gave no answer |
Source | Rating | Number of reviews |
|---|---|---|
TrustPilot | 1/5 | 1 |
Source | Rating | Main topic | Sentiment |
|---|---|---|---|
TrustPilot | 1/5 | Post-cancel billing | Negative |
Only negative review evidence was supplied here. To balance that fairly, Azure’s positive side is its broad feature set and detailed official cancellation documentation on Microsoft Learn. The weak spot is billing clarity when multiple resources are involved.
If you want a smooth exit, gather evidence before touching anything. Save a screenshot of your subscription name, plan type, billing date, and account email. Also capture the list of active Azure resources, because later disputes often turn on whether a resource was still running on a specific date.
For a refund request, you need transaction IDs, invoice numbers, payment dates, and the exact amount charged in RM. If you deleted a resource, capture the deletion confirmation or activity log entry. These details are much stronger than a general complaint saying you think the bill looks wrong.
After cancellation, save the confirmation page, confirmation email, support case ID, and updated bank or card statement. Check again after the next billing date to make sure no fresh recurring charge has appeared.
This is the classic Azure problem. A user cancels a support plan or deletes one app, but a SQL database, storage account, or VM keeps running. The review in the supplied data points to this exact frustration. Solution: compare your invoice lines with your active resource list before and after cancellation.
If an invoice shows database charges, verify the database service itself is gone and not only disconnected. In Azure, silence is not proof. The portal must show the resource as deleted or inactive.
Many users assume they will get money back for unused days. In Malaysia, Microsoft says no prorated refund is available for unused periods "support.microsoft.com". Solution: cancel before the next billing date if your goal is to avoid the next charge. Do not rely on a mid-cycle refund.
For longer commitments, the supplied agreement data is even stricter. After 30 days, you may still owe the rest of the term "azure.microsoft.com". That is why checking commitment length before cancellation is so important.
If the portal confirms cancellation and you do not save it, you create unnecessary trouble for yourself. Later, support may ask when you cancelled, and memory is not enough. Solution: keep screenshots, email confirmation, and any support ticket references on the same day.
A simple folder with the cancellation date in the filename can save hours later. This matters a lot if you need to complain to KPDN, TTPM, or your bank.
Some people jump straight to a bank dispute without opening a Microsoft case first. That can weaken the paper trail. Solution: start with Microsoft support through the portal, then escalate to KPDN, TTPM, or your bank if the answer is poor or the charge is clearly unauthorised.
On the other side, do not wait too long either. Bank disputes often work within roughly 60 to 120 days. If the charge is fresh, start collecting evidence immediately.
Method | Notice period | Fee | Difficulty |
|---|---|---|---|
Web/account | Before next billing | No fee specified | Easy |
Registered mail | 5-10 business days | No fee specified | Higher but strong proof |
Portal support case | Before next billing | No fee specified | Medium |
The web account route is the fastest if you simply want to stop future billing. A support case is useful when billing is already wrong or a resource charge is unclear. Registered mail is slower, but it gives useful proof if the dispute becomes formal.
No single method fits every case. If your account is straightforward, the account page is enough. If your bill is messy, combine account cancellation with a support case and keep written proof.
Right after cancelling, confirm the subscription status changed in your account, save screenshots, and set a calendar reminder for the next billing date plus 3 days. Then review your card or bank statement after that date. If a recurring charge appears, compare the amount with the disputed service or resource line on the invoice.
If the charge is unauthorised or clearly post-cancellation, ask your bank for a chargeback or card transaction dispute. In Malaysia, this is usually handled by the issuing bank, commonly within about 60 to 120 days from the transaction or discovery of the problem, under Bank Negara Malaysia complaint-handling rules.
If you are cancelling because of cost or complexity, there are workable alternatives. Amazon Web Services and Google Cloud Platform both use pay-as-you-go models with broad enterprise features. DigitalOcean is often easier for smaller teams and simpler workloads, with Droplets from $4.00 (RM19)* per month and App Platform from $5.00 (RM24)* per month from the supplied alternative data.
IBM Cloud and Oracle Cloud Infrastructure are also options if you need enterprise tooling. The right move depends on whether your issue is price, support, or portal complexity. For many smaller Malaysian users, simpler billing is often the real priority.
If you want to send a written cancellation notice, billing dispute summary, or supporting documents, use Microsoft’s Malaysia office address below. Online account cancellation is still the main route, but a physical letter can help build a clean evidence trail.
The address is:
Include your full name, Microsoft account email, subscription name, invoice reference, disputed amount if any, and the date you want the cancellation recognised.
Use the postal address when the portal route has already been tried, when a billing dispute needs stronger proof, or when you are preparing a complaint for KPDN or TTPM. Send copies, not original identity documents. Keep the tracking proof and attach it to your complaint file if the issue is still not resolved.
For most users, the fastest route is still online cancellation through Services & subscriptions, followed by a portal support case if charges continue. The postal route is a backup with stronger documentation, not a replacement for checking the account itself.
Already sent a letter? Enter its tracking number to see its proof of dispatch and certified timestamp.