{"id":59257,"date":"2026-10-20T06:59:06","date_gmt":"2026-10-19T20:59:06","guid":{"rendered":"https:\/\/www.cloudproinc.com.au\/index.php\/2026\/10\/20\/sql-server-october-2026-patching-and-modernisation-checklist\/"},"modified":"2026-10-20T07:00:18","modified_gmt":"2026-10-19T21:00:18","slug":"sql-server-october-2026-patching-and-modernisation-checklist","status":"publish","type":"post","link":"https:\/\/www.cloudproinc.com.au\/index.php\/2026\/10\/20\/sql-server-october-2026-patching-and-modernisation-checklist\/","title":{"rendered":"SQL Server October 2026 Patching and Modernisation Checklist"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">In this blog post SQL Server October 2026 Patching and Modernisation Checklist we will show IT managers how to close the latest security gaps without turning a routine update into an ERP outage, broken reporting system or weekend-long recovery exercise.<\/p>\n\n\n\n<!--more-->\n\n\n\n<p class=\"wp-block-paragraph\">SQL Server often sits quietly behind finance, payroll, inventory, customer management and operational systems. When it is unpatched, attackers may have a path to sensitive business data. When it is patched without proper testing, the applications your staff depend on can stop working.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What the October SQL Server patch wave actually does<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">SQL Server is Microsoft&#8217;s database platform. It stores information, controls who can access it and processes requests from business applications.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">On 13 October 2026, Microsoft released eight security packages covering SQL Server 2017, 2019, 2022 and 2025. They address multiple types of weakness, including flaws that could allow an attacker to run unauthorised commands, gain higher access, expose information or disrupt database services.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">There are different packages because Microsoft maintains two update paths. A General Distribution Release, or GDR, mainly provides security fixes. A Cumulative Update, or CU, includes security fixes plus other reliability and performance improvements.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Your team must install the package matching the update path already used by each server. Choosing the wrong package or assuming every SQL Server is identical creates unnecessary risk.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For a closer look at the immediate update risks, read what the October 2026 SQL Server updates mean in Australia. The checklist below focuses on making patching repeatable and using this event to address ageing database infrastructure.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">1. Find every SQL Server before changing anything<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The first problem is often not patch deployment. It is that nobody has a complete list of the SQL Servers supporting the business.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Include production, testing, reporting and disaster recovery servers. Look for forgotten SQL Express installations bundled with accounting software, access-control systems, manufacturing applications and monitoring tools.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For every instance, record:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>SQL Server version, edition, build and update path<\/li>\n<li>Server location and whether it is internet-facing<\/li>\n<li>Applications, departments and business processes that depend on it<\/li>\n<li>Database owner and technical support contact<\/li>\n<li>Backup method, recovery target and last successful restore test<\/li>\n<li>Support status and planned replacement date<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Your database administrator can run this basic query to collect version details:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>SELECT\n SERVERPROPERTY(&#39;MachineName&#39;) AS ServerName,\n SERVERPROPERTY(&#39;InstanceName&#39;) AS InstanceName,\n SERVERPROPERTY(&#39;ProductVersion&#39;) AS ProductVersion,\n SERVERPROPERTY(&#39;ProductLevel&#39;) AS ProductLevel,\n SERVERPROPERTY(&#39;Edition&#39;) AS Edition;<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">This inventory reduces the chance of leaving an exposed server behind. It also gives management a clear view of which systems create the greatest financial and operational risk.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">2. Treat unsupported versions as a business decision<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">SQL Server 2016 reached the end of normal Microsoft support on 14 July 2026. It is not covered by the standard October update wave unless the organisation has arranged eligible Extended Security Updates, known as ESUs.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">ESUs are paid security updates designed to buy time while an organisation upgrades or migrates. They are not a long-term modernisation plan, and they do not provide the full range of product fixes available for supported versions.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">SQL Server 2017 is also approaching extended support expiry on 12 October 2027. If it runs a critical application, waiting until next year&#8217;s deadline will leave little room for application testing, budgeting and vendor coordination.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ask three management-level questions:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Is the application still supported on a current SQL Server release?<\/li>\n<li>What would one day of database downtime cost the business?<\/li>\n<li>Are we paying to preserve an old platform when that money could fund its replacement?<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">3. Prove recovery before approving the patch<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A green backup report does not prove that the database can be restored. Before patching, restore a recent backup into an isolated test environment and confirm that the application can read its data.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The recovery check should cover user databases, system databases, encryption keys, certificates and any transaction logs needed to meet your recovery target. For clustered or highly available systems, document which node will be patched first and how the service will fail over if something goes wrong.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Also confirm that rollback decisions have owners and time limits. Repeatedly uninstalling security updates or restoring snapshots without understanding database activity can create data consistency problems.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is why mid-market patch validation cannot be optional. Recovery testing converts hope into evidence.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">4. Test the connections around SQL Server<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Most post-update incidents occur in the systems around the database rather than the database itself. That includes backup software, reporting tools, ERP integrations, scheduled jobs and third-party connection drivers.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Pay particular attention to linked servers. A linked server allows one database to retrieve information from another SQL Server or an external platform such as Oracle, MySQL or a legacy business system.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you use MSDASQL linked servers, which connect SQL Server to other systems through ODBC drivers, test them with normal non-administrator accounts. Microsoft has documented error 7416 across 2026 servicing branches, and your exact patch, driver and login configuration still requires validation.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>SELECT name, provider, data_source\nFROM sys.servers\nWHERE is_linked = 1;<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Do not solve a connection problem by granting users full SQL Server administrator rights. That may restore a report quickly, but it creates a much larger security exposure.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">5. Deploy in stages and test real business tasks<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Start with a representative test server. If that succeeds, patch a lower-risk production instance or passive cluster node before updating the most important databases.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Your validation should test business outcomes, not just whether the SQL Server service started. Confirm that staff can:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Sign in to critical applications<\/li>\n<li>Create and update transactions<\/li>\n<li>Run finance, payroll and operational reports<\/li>\n<li>Complete integrations and scheduled data transfers<\/li>\n<li>Perform backups and monitoring checks<\/li>\n<li>Fail over to the secondary system where applicable<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">After deployment, verify the new build number and watch database errors, failed jobs, login failures, application response times and backup results for at least one full business cycle.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This staged process supports Essential 8, the Australian government&#8217;s cybersecurity framework that many organisations are expected to follow. ASD guidance calls for critical or actively exploited vulnerabilities to be patched or otherwise mitigated quickly, sometimes within 48 hours. Fast patching still requires disciplined validation.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">A practical mid-market scenario<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Consider a 200-person company running its finance and inventory platform on SQL Server 2016. Management believes it has one database server, but the patch inventory discovers a second reporting instance and a legacy integration using an old linked-server driver.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Testing shows the core application works after the update, but a daily stock report fails under its normal service account. Because the team tested before production, it corrects the connection configuration without delaying warehouse operations.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The same review reveals that SQL Server 2016 is outside normal support. Rather than paying indefinitely to preserve it, the company approves a staged move to a supported platform, reducing both security exposure and the risk of an emergency migration.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">6. Turn patching into a modernisation decision<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Patching closes known security gaps, but it does not fix an unsupported operating model. Use the October review to choose a practical destination for each important workload.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Upgrade on-premises<\/strong> when the application must remain local and its vendor supports a current SQL Server version.<\/li>\n<li><strong>Move to SQL Server on an Azure virtual machine<\/strong> when you need a familiar environment with minimal application changes, while accepting that your team still manages much of the patching.<\/li>\n<li><strong>Move to Azure SQL Managed Instance<\/strong>, a managed database service with broad SQL Server compatibility, when you want Microsoft to handle more of the backups, maintenance and platform availability.<\/li>\n<li><strong>Use Azure SQL Database<\/strong> for applications that can be redesigned around a fully managed database, reducing server administration further.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The right option depends on application compatibility, downtime tolerance, licensing, compliance and cost. A migration assessment should compare several years of operating expense, not simply this year&#8217;s cloud bill against an already-purchased server.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Your 30-day action checklist<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Complete an inventory of every SQL Server instance.<\/li>\n<li>Confirm the correct October 2026 package for each supported server.<\/li>\n<li>Identify SQL Server 2016 systems without active ESU coverage.<\/li>\n<li>Start an upgrade plan for business-critical SQL Server 2017 workloads.<\/li>\n<li>Prove that backups can be restored.<\/li>\n<li>Test linked servers, drivers, jobs, reporting and application transactions.<\/li>\n<li>Deploy through test, lower-risk and critical environments in stages.<\/li>\n<li>Record post-patch evidence for Essential 8 and audit requirements.<\/li>\n<li>Assign an owner, budget and target date to every unsupported platform.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Patching should reduce risk, not move it from cybersecurity into operations. The safest organisations know what they run, can recover it and use each security event to remove ageing systems from the environment.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">CloudProInc brings more than 20 years of enterprise IT experience to this work, backed by practical Microsoft Partner and Wiz Security Integrator capability across SQL Server, Azure and cybersecurity. If you are unsure whether every database is patched, recoverable and properly supported, our Melbourne-based team is happy to take a look with you \u2014 no strings attached.<\/p>\n\n\n","protected":false},"excerpt":{"rendered":"<p>Use this practical checklist to patch SQL Server safely, test critical integrations, meet Essential 8 expectations and decide whether ageing database platforms should be upgraded or moved to Azure.<\/p>\n","protected":false},"author":1,"featured_media":59259,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":true,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[131,13,107,138],"tags":[],"class_list":["post-59257","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-backup-disaster-recovery","category-blog","category-cybersecurity","category-sql-server"],"jetpack-related-posts":[{"id":59204,"url":"https:\/\/www.cloudproinc.com.au\/index.php\/2026\/10\/19\/patch-now-what-october-2026-sql-server-updates-mean-in-australia\/","url_meta":{"origin":59257,"position":0},"title":"Patch Now What October 2026 SQL Server Updates Mean in Australia","author":"CPI Staff","date":"October 19, 2026","format":false,"excerpt":"Microsoft\u2019s October 2026 SQL Server updates close serious security gaps but may disrupt some linked-server connections. Here is a practical patching plan for Australian mid-market teams.","rel":"","context":"In &quot;Blog&quot;","block_context":{"text":"Blog","link":"https:\/\/www.cloudproinc.com.au\/index.php\/category\/blog\/"},"img":{"alt_text":"","src":"\/wp-content\/uploads\/2026\/10\/patch-now-what-october-2026-sql-server-updates-mean-in-australia.png","width":350,"height":200,"srcset":"\/wp-content\/uploads\/2026\/10\/patch-now-what-october-2026-sql-server-updates-mean-in-australia.png 1x, \/wp-content\/uploads\/2026\/10\/patch-now-what-october-2026-sql-server-updates-mean-in-australia.png 1.5x, \/wp-content\/uploads\/2026\/10\/patch-now-what-october-2026-sql-server-updates-mean-in-australia.png 2x, \/wp-content\/uploads\/2026\/10\/patch-now-what-october-2026-sql-server-updates-mean-in-australia.png 3x, \/wp-content\/uploads\/2026\/10\/patch-now-what-october-2026-sql-server-updates-mean-in-australia.png 4x"},"classes":[]},{"id":59225,"url":"https:\/\/www.cloudproinc.com.au\/index.php\/2026\/10\/19\/from-migration-factory-to-a-secure-azure-landing-zone-at-scale\/","url_meta":{"origin":59257,"position":1},"title":"From Migration Factory to a Secure Azure Landing Zone at Scale","author":"CPI Staff","date":"October 19, 2026","format":false,"excerpt":"Learn how to turn server migration into a repeatable, secure Azure program that reduces risk, controls cost and creates a better platform for future modernisation.","rel":"","context":"In &quot;Azure&quot;","block_context":{"text":"Azure","link":"https:\/\/www.cloudproinc.com.au\/index.php\/category\/microsoft-azure\/"},"img":{"alt_text":"","src":"\/wp-content\/uploads\/2026\/10\/from-migration-factory-to-a-secure-azure-landing-zone-at-scale.png","width":350,"height":200,"srcset":"\/wp-content\/uploads\/2026\/10\/from-migration-factory-to-a-secure-azure-landing-zone-at-scale.png 1x, \/wp-content\/uploads\/2026\/10\/from-migration-factory-to-a-secure-azure-landing-zone-at-scale.png 1.5x, \/wp-content\/uploads\/2026\/10\/from-migration-factory-to-a-secure-azure-landing-zone-at-scale.png 2x, \/wp-content\/uploads\/2026\/10\/from-migration-factory-to-a-secure-azure-landing-zone-at-scale.png 3x, \/wp-content\/uploads\/2026\/10\/from-migration-factory-to-a-secure-azure-landing-zone-at-scale.png 4x"},"classes":[]},{"id":58575,"url":"https:\/\/www.cloudproinc.com.au\/index.php\/2026\/10\/12\/how-to-design-zone-resilient-azure-sql-managed-instance-workloads\/","url_meta":{"origin":59257,"position":2},"title":"How to Design Zone-Resilient Azure SQL Managed Instance Workloads","author":"CPI Staff","date":"October 12, 2026","format":false,"excerpt":"Learn how to protect Azure SQL Managed Instance workloads from data centre outages without creating an expensive, difficult-to-manage recovery architecture.","rel":"","context":"In &quot;Azure&quot;","block_context":{"text":"Azure","link":"https:\/\/www.cloudproinc.com.au\/index.php\/category\/microsoft-azure\/"},"img":{"alt_text":"","src":"\/wp-content\/uploads\/2026\/08\/how-to-design-zone-resilient-azure-sql-managed-instance-workloads.png","width":350,"height":200,"srcset":"\/wp-content\/uploads\/2026\/08\/how-to-design-zone-resilient-azure-sql-managed-instance-workloads.png 1x, \/wp-content\/uploads\/2026\/08\/how-to-design-zone-resilient-azure-sql-managed-instance-workloads.png 1.5x, \/wp-content\/uploads\/2026\/08\/how-to-design-zone-resilient-azure-sql-managed-instance-workloads.png 2x, \/wp-content\/uploads\/2026\/08\/how-to-design-zone-resilient-azure-sql-managed-instance-workloads.png 3x, \/wp-content\/uploads\/2026\/08\/how-to-design-zone-resilient-azure-sql-managed-instance-workloads.png 4x"},"classes":[]},{"id":59173,"url":"https:\/\/www.cloudproinc.com.au\/index.php\/2026\/10\/18\/is-your-exchange-server-patched-october-2026-security-checklist\/","url_meta":{"origin":59257,"position":3},"title":"Is Your Exchange Server Patched October 2026 Security Checklist","author":"CPI Staff","date":"October 18, 2026","format":false,"excerpt":"Use this practical October 2026 checklist to confirm Exchange patch status, avoid update-related disruption and address the end of security support for Exchange 2016 and 2019.","rel":"","context":"In &quot;Blog&quot;","block_context":{"text":"Blog","link":"https:\/\/www.cloudproinc.com.au\/index.php\/category\/blog\/"},"img":{"alt_text":"","src":"\/wp-content\/uploads\/2026\/10\/is-your-exchange-server-patched-october-2026-security-checklist.png","width":350,"height":200,"srcset":"\/wp-content\/uploads\/2026\/10\/is-your-exchange-server-patched-october-2026-security-checklist.png 1x, \/wp-content\/uploads\/2026\/10\/is-your-exchange-server-patched-october-2026-security-checklist.png 1.5x, \/wp-content\/uploads\/2026\/10\/is-your-exchange-server-patched-october-2026-security-checklist.png 2x, \/wp-content\/uploads\/2026\/10\/is-your-exchange-server-patched-october-2026-security-checklist.png 3x, \/wp-content\/uploads\/2026\/10\/is-your-exchange-server-patched-october-2026-security-checklist.png 4x"},"classes":[]},{"id":59093,"url":"https:\/\/www.cloudproinc.com.au\/index.php\/2026\/10\/14\/immutable-azure-sql-backups-for-practical-ransomware-recovery\/","url_meta":{"origin":59257,"position":4},"title":"Immutable Azure SQL Backups for Practical Ransomware Recovery","author":"CPI Staff","date":"October 14, 2026","format":false,"excerpt":"Learn how to design tamper-resistant Azure SQL backups that protect recovery points, support Essential 8 goals and give leaders confidence the business can recover.","rel":"","context":"In &quot;Azure&quot;","block_context":{"text":"Azure","link":"https:\/\/www.cloudproinc.com.au\/index.php\/category\/microsoft-azure\/"},"img":{"alt_text":"","src":"\/wp-content\/uploads\/2026\/10\/immutable-azure-sql-backups-for-practical-ransomware-recovery.png","width":350,"height":200,"srcset":"\/wp-content\/uploads\/2026\/10\/immutable-azure-sql-backups-for-practical-ransomware-recovery.png 1x, \/wp-content\/uploads\/2026\/10\/immutable-azure-sql-backups-for-practical-ransomware-recovery.png 1.5x, \/wp-content\/uploads\/2026\/10\/immutable-azure-sql-backups-for-practical-ransomware-recovery.png 2x, \/wp-content\/uploads\/2026\/10\/immutable-azure-sql-backups-for-practical-ransomware-recovery.png 3x, \/wp-content\/uploads\/2026\/10\/immutable-azure-sql-backups-for-practical-ransomware-recovery.png 4x"},"classes":[]},{"id":59207,"url":"https:\/\/www.cloudproinc.com.au\/index.php\/2026\/10\/19\/october-patch-tuesday-exchange-server-stabilisation-checklist\/","url_meta":{"origin":59257,"position":5},"title":"October Patch Tuesday Exchange Server Stabilisation Checklist","author":"CPI Staff","date":"October 19, 2026","format":false,"excerpt":"A practical post-patch checklist to restore Exchange stability, protect mail flow and turn October 2026 update disruption into a safer patching process.","rel":"","context":"In &quot;Blog&quot;","block_context":{"text":"Blog","link":"https:\/\/www.cloudproinc.com.au\/index.php\/category\/blog\/"},"img":{"alt_text":"","src":"\/wp-content\/uploads\/2026\/10\/october-patch-tuesday-exchange-server-stabilisation-checklist.png","width":350,"height":200,"srcset":"\/wp-content\/uploads\/2026\/10\/october-patch-tuesday-exchange-server-stabilisation-checklist.png 1x, \/wp-content\/uploads\/2026\/10\/october-patch-tuesday-exchange-server-stabilisation-checklist.png 1.5x, \/wp-content\/uploads\/2026\/10\/october-patch-tuesday-exchange-server-stabilisation-checklist.png 2x, \/wp-content\/uploads\/2026\/10\/october-patch-tuesday-exchange-server-stabilisation-checklist.png 3x, \/wp-content\/uploads\/2026\/10\/october-patch-tuesday-exchange-server-stabilisation-checklist.png 4x"},"classes":[]}],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"\/wp-content\/uploads\/2026\/10\/sql-server-october-2026-patching-and-modernisation-checklist.png","_links":{"self":[{"href":"https:\/\/www.cloudproinc.com.au\/index.php\/wp-json\/wp\/v2\/posts\/59257","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cloudproinc.com.au\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cloudproinc.com.au\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cloudproinc.com.au\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cloudproinc.com.au\/index.php\/wp-json\/wp\/v2\/comments?post=59257"}],"version-history":[{"count":1,"href":"https:\/\/www.cloudproinc.com.au\/index.php\/wp-json\/wp\/v2\/posts\/59257\/revisions"}],"predecessor-version":[{"id":59258,"href":"https:\/\/www.cloudproinc.com.au\/index.php\/wp-json\/wp\/v2\/posts\/59257\/revisions\/59258"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.cloudproinc.com.au\/index.php\/wp-json\/wp\/v2\/media\/59259"}],"wp:attachment":[{"href":"https:\/\/www.cloudproinc.com.au\/index.php\/wp-json\/wp\/v2\/media?parent=59257"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cloudproinc.com.au\/index.php\/wp-json\/wp\/v2\/categories?post=59257"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cloudproinc.com.au\/index.php\/wp-json\/wp\/v2\/tags?post=59257"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}