{"id":12972,"date":"2025-08-07T16:47:50","date_gmt":"2025-08-07T16:47:50","guid":{"rendered":"https:\/\/www.itarian.com\/blog\/?p=12972"},"modified":"2025-08-07T16:47:50","modified_gmt":"2025-08-07T16:47:50","slug":"how-to-block-sign-of-non-m365-emails","status":"publish","type":"post","link":"https:\/\/www.itarian.com\/blog\/how-to-block-sign-of-non-m365-emails\/","title":{"rendered":"How to Block Sign-In of Non-M365 Emails: Secure Your Microsoft 365 Environment"},"content":{"rendered":"<p><span style=\"font-weight: 400;\">Do you want to <\/span><b>stop unauthorized access attempts<\/b><span style=\"font-weight: 400;\"> from email addresses outside your trusted Microsoft 365 domain? If you&#8217;re asking, <\/span><b>&#8220;how to block sign of non M365 emails,&#8221;<\/b><span style=\"font-weight: 400;\"> you&#8217;re taking the right step toward securing your organization&#8217;s cloud environment.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Whether you&#8217;re a cybersecurity professional monitoring identity threats or an IT manager responsible for user governance, controlling sign-ins from <\/span><b>non-Microsoft 365 (M365)<\/b><span style=\"font-weight: 400;\"> accounts is essential for maintaining <\/span><b>data integrity, compliance, and zero-trust security<\/b><span style=\"font-weight: 400;\">.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">In this guide, we\u2019ll explore <\/span><b>multiple ways to block sign-ins of non-M365 emails<\/b><span style=\"font-weight: 400;\">, leveraging <\/span><b>Azure AD Conditional Access<\/b><span style=\"font-weight: 400;\">, <\/span><b>Exchange Online policies<\/b><span style=\"font-weight: 400;\">, and <\/span><b>tenant restrictions<\/b><span style=\"font-weight: 400;\">. Let\u2019s secure your digital workspace\u2014one policy at a time.<\/span><\/p>\n<h2><b>Why You Should Block Sign-Ins from Non-M365 Accounts<\/b><\/h2>\n<p><b>Microsoft 365<\/b><span style=\"font-weight: 400;\"> environments are under constant threat from:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Phishing attacks using spoofed domains<\/span>&nbsp;<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Shadow IT usage via personal email accounts<\/span>&nbsp;<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Unauthorized access from unmanaged identities<\/span>&nbsp;<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Insider threats accessing sensitive info from external addresses<\/span>&nbsp;<\/li>\n<\/ul>\n<h3><b>Blocking non-M365 sign-ins helps to:<\/b><\/h3>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Strengthen organizational identity perimeter<\/span>&nbsp;<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Ensure that only corporate emails are used for access<\/span>&nbsp;<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Reduce the attack surface<\/span>&nbsp;<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Comply with data protection regulations and audits<\/span>&nbsp;<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Block personal or rogue accounts from signing into apps like Teams, SharePoint, or Outlook<\/span>&nbsp;<\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">Taking control of <\/span><b>how to block sign of non M365 emails<\/b><span style=\"font-weight: 400;\"> improves both <\/span><b>compliance<\/b><span style=\"font-weight: 400;\"> and <\/span><b>cyber resilience<\/b><span style=\"font-weight: 400;\">.<\/span><\/p>\n<h2><b>Key Terms to Understand<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Before implementing any restrictions, it\u2019s important to clarify:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>M365 Accounts<\/b><span style=\"font-weight: 400;\">: Users with email addresses hosted under your organization\u2019s Microsoft 365 domain (e.g., user@company.com)<\/span>&nbsp;<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Non-M365 Accounts<\/b><span style=\"font-weight: 400;\">: Includes personal Outlook.com, Gmail, Yahoo, or any non-authorized business accounts<\/span>&nbsp;<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Conditional Access<\/b><span style=\"font-weight: 400;\">: Azure AD tool used to enforce policies around user sign-ins and app access<\/span>&nbsp;<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Tenant Restrictions<\/b><span style=\"font-weight: 400;\">: Feature to restrict Microsoft 365 apps from connecting to other tenants<\/span>&nbsp;<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>External Identities<\/b><span style=\"font-weight: 400;\">: Users invited via Azure AD B2B or federation<\/span>&nbsp;<\/li>\n<\/ul>\n<h2><b>How to Block Sign-In of Non-M365 Emails Using Azure AD<\/b><\/h2>\n<h3><b>Step 1: Create a Conditional Access Policy<\/b><\/h3>\n<p><b>Azure AD Conditional Access<\/b><span style=\"font-weight: 400;\"> is the most powerful way to block or control sign-ins from external users.<\/span><\/p>\n<h4><b>Steps:<\/b><\/h4>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Sign in to the <\/span><b>Azure portal<\/b><span style=\"font-weight: 400;\"> (https:\/\/portal.azure.com)<\/span>&nbsp;<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Navigate to <\/span><b>Azure Active Directory &gt; Security &gt; Conditional Access<\/b>&nbsp;<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Click <\/span><b>New Policy<\/b>&nbsp;<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Name the policy (e.g., \u201cBlock Non-M365 Sign-Ins\u201d)<\/span>&nbsp;<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Under <\/span><b>Assignments<\/b><span style=\"font-weight: 400;\">, choose <\/span><b>All users<\/b><span style=\"font-weight: 400;\"> or a specific group<\/span>&nbsp;<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Under <\/span><b>Cloud apps<\/b><span style=\"font-weight: 400;\">, select <\/span><b>All cloud apps<\/b>&nbsp;<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">In <\/span><b>Conditions<\/b><span style=\"font-weight: 400;\">, go to <\/span><b>Locations &gt; Configure<\/b><span style=\"font-weight: 400;\"> and select \u201c<\/span><b>Exclude trusted locations<\/b><span style=\"font-weight: 400;\">\u201d<\/span>&nbsp;<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Under <\/span><b>Access Controls &gt; Grant<\/b><span style=\"font-weight: 400;\">, choose <\/span><b>Block access<\/b>&nbsp;<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Enable the policy and click <\/span><b>Create<\/b>&nbsp;<\/li>\n<\/ol>\n<p><span style=\"font-weight: 400;\">This policy prevents users from signing in outside of approved domains or regions.<\/span><\/p>\n<h2><b>Use Tenant Restrictions to Prevent Cross-Tenant Logins<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Tenant restrictions help stop users in your network from signing into <\/span><b>external Microsoft 365 tenants<\/b><span style=\"font-weight: 400;\">, including personal or competitor accounts.<\/span><\/p>\n<h3><b>Requirements:<\/b><\/h3>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Windows 10\/11 Enterprise<\/span>&nbsp;<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Enforced via registry or Group Policy<\/span>&nbsp;<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Device must be domain-joined and use modern authentication<\/span>&nbsp;<\/li>\n<\/ul>\n<h3><b>How to Implement:<\/b><\/h3>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Open <\/span><b>Group Policy Editor<\/b>&nbsp;<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Go to <\/span><b>Computer Configuration &gt; Administrative Templates &gt; Microsoft Edge<\/b>&nbsp;<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Enable policy:<\/span>&nbsp;\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"2\"><b>\u201cSet tenant restrictions for Microsoft cloud apps\u201d<\/b>&nbsp;<\/li>\n<\/ul>\n<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Add your organization&#8217;s tenant ID as <\/span><b>AllowedTenant<\/b>&nbsp;<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Block all other tenants by setting <\/span><b>BlockedTenant<\/b><span style=\"font-weight: 400;\"> to <\/span><span style=\"font-weight: 400;\">*<\/span><span style=\"font-weight: 400;\"> (wildcard)<\/span>&nbsp;<\/li>\n<\/ol>\n<h3><b>Registry Option:<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">reg<\/span><\/p>\n<p><span style=\"font-weight: 400;\">CopyEdit<\/span><\/p>\n<p><span style=\"font-weight: 400;\">[HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Microsoft\\Edge\\CloudApps\\TenantRestrictions]<\/span><\/p>\n<p><span style=\"font-weight: 400;\">&#8220;AllowedTenants&#8221;=&#8221;yourtenantID&#8221;<\/span><\/p>\n<p><span style=\"font-weight: 400;\">&#8220;BlockedTenants&#8221;=&#8221;*&#8221;<\/span><\/p>\n<p>&nbsp;<\/p>\n<p><span style=\"font-weight: 400;\">This prevents M365 applications like Teams, SharePoint, and OneDrive from authenticating against untrusted tenants.<\/span><\/p>\n<h2><b>Prevent Guest or External B2B Users from Accessing Apps<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">If you&#8217;re using <\/span><b>Azure AD B2B Collaboration<\/b><span style=\"font-weight: 400;\">, you can restrict access for non-M365 accounts by controlling guest access.<\/span><\/p>\n<h3><b>Option 1: Turn Off Guest Access in Microsoft 365<\/b><\/h3>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Go to <\/span><b>Microsoft 365 Admin Center<\/b>&nbsp;<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Navigate to <\/span><b>Org settings &gt; Services &gt; Microsoft Teams \/ SharePoint \/ Groups<\/b>&nbsp;<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Disable <\/span><b>\u201cAllow guest access\u201d<\/b>&nbsp;<\/li>\n<\/ol>\n<h3><b>Option 2: Use Azure AD External Collaboration Settings<\/b><\/h3>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Go to <\/span><b>Azure AD &gt; External Identities &gt; External collaboration settings<\/b>&nbsp;<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Configure policies like:<\/span>&nbsp;\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"2\"><span style=\"font-weight: 400;\">Only allow invitations to specific domains<\/span>&nbsp;<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"2\"><span style=\"font-weight: 400;\">Deny invitations from free email providers<\/span>&nbsp;<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n<p><span style=\"font-weight: 400;\">Be cautious\u2014blocking too broadly may restrict vendor or partner integrations.<\/span><\/p>\n<h2><b>Block Email Domains Using Exchange Online Mail Flow Rules<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">You can create <\/span><b>transport rules<\/b><span style=\"font-weight: 400;\"> (also called mail flow rules) in <\/span><b>Exchange Online<\/b><span style=\"font-weight: 400;\"> to block sign-ins associated with unauthorized domains.<\/span><\/p>\n<h3><b>Steps:<\/b><\/h3>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Open <\/span><b>Exchange Admin Center<\/b><span style=\"font-weight: 400;\"> (https:\/\/admin.exchange.microsoft.com)<\/span>&nbsp;<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Go to <\/span><b>Mail flow &gt; Rules<\/b>&nbsp;<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Create a new rule named <\/span><b>Block Personal Email Domains<\/b>&nbsp;<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Conditions:<\/span>&nbsp;\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"2\"><span style=\"font-weight: 400;\">\u201cThe sender is located outside the organization\u201d<\/span>&nbsp;<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"2\"><span style=\"font-weight: 400;\">\u201cThe sender\u2019s domain is&#8230;\u201d (e.g., gmail.com, yahoo.com)<\/span>&nbsp;<\/li>\n<\/ul>\n<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Action: <\/span><b>Reject the message with explanation<\/b>&nbsp;<\/li>\n<\/ol>\n<p><span style=\"font-weight: 400;\">\ud83d\udce7 While this doesn\u2019t block sign-ins directly, it prevents unauthorized use of email from personal accounts in communication chains.<\/span><\/p>\n<h2><b>Best Practices to Block Non-M365 Sign-Ins<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">To effectively manage sign-in restrictions, follow these guidelines:<\/span><\/p>\n<h3><b>Do:<\/b><\/h3>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Define and enforce a list of <\/span><b>approved domains<\/b>&nbsp;<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Regularly audit sign-in logs in <\/span><b>Azure AD &gt; Sign-ins<\/b>&nbsp;<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Use <\/span><b>Multi-Factor Authentication (MFA)<\/b><span style=\"font-weight: 400;\"> for added protection<\/span>&nbsp;<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Enable <\/span><b>Sign-in Risk policies<\/b><span style=\"font-weight: 400;\"> for suspicious logins<\/span>&nbsp;<\/li>\n<\/ul>\n<h3><b>Don\u2019t:<\/b><\/h3>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Rely only on email domain blacklisting\u2014it can be spoofed<\/span>&nbsp;<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Allow unrestricted guest invitations<\/span>&nbsp;<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Skip policy testing\u2014always simulate before rollout<\/span>&nbsp;<\/li>\n<\/ul>\n<h2><b>Monitor and Report Suspicious Sign-Ins<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Use Microsoft Defender for Cloud Apps or Microsoft 365 Security Center to:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Set up alerts for <\/span><b>logins from unknown tenants<\/b>&nbsp;<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Monitor <\/span><b>impossible travel<\/b><span style=\"font-weight: 400;\"> or <\/span><b>unfamiliar sign-in patterns<\/b>&nbsp;<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">View sign-in attempts via <\/span><b>Audit Logs<\/b>&nbsp;<\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">Visibility is key. Even with blocking in place, ongoing monitoring ensures proactive defense.<\/span><\/p>\n<h2><b>FAQs: Blocking Non-M365 Email Sign-Ins<\/b><\/h2>\n<h3><b>1. Can I completely block personal Gmail or Yahoo logins?<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Yes. Use <\/span><b>tenant restrictions<\/b><span style=\"font-weight: 400;\"> and <\/span><b>conditional access<\/b><span style=\"font-weight: 400;\"> policies to enforce this.<\/span><\/p>\n<h3><b>2. Is it possible to allow B2B collaboration while still blocking personal accounts?<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Yes. Use <\/span><b>Azure AD External Identities<\/b><span style=\"font-weight: 400;\"> to allow domains like <\/span><span style=\"font-weight: 400;\">partnercompany.com<\/span><span style=\"font-weight: 400;\"> but deny <\/span><span style=\"font-weight: 400;\">gmail.com<\/span><span style=\"font-weight: 400;\">.<\/span><\/p>\n<h3><b>3. What happens if I block a legitimate external login by accident?<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Always start with <\/span><b>report-only mode<\/b><span style=\"font-weight: 400;\"> for Conditional Access policies to avoid disruptions.<\/span><\/p>\n<h3><b>4. Can a user still access M365 apps on a personal device?<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Only if the Conditional Access policy allows it. You can restrict by device compliance or require <\/span><b>enrollment in Intune<\/b><span style=\"font-weight: 400;\">.<\/span><\/p>\n<h3><b>5. Do tenant restrictions apply to mobile apps?<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Yes, if devices are <\/span><b>Azure AD joined<\/b><span style=\"font-weight: 400;\"> or use <\/span><b>modern authentication<\/b><span style=\"font-weight: 400;\"> with supported apps.<\/span><\/p>\n<h2><b>Final Thoughts<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Implementing secure sign-in policies is no longer optional\u2014it\u2019s a foundational component of <\/span><b>zero trust architecture<\/b><span style=\"font-weight: 400;\">. If you&#8217;re wondering <\/span><b>how to block sign of non M365 emails<\/b><span style=\"font-weight: 400;\">, you now have multiple robust tools at your disposal\u2014from <\/span><b>Azure Conditional Access<\/b><span style=\"font-weight: 400;\"> to <\/span><b>tenant restrictions<\/b><span style=\"font-weight: 400;\"> and <\/span><b>mail flow policies<\/b><span style=\"font-weight: 400;\">.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">By enforcing domain restrictions, disabling external access, and auditing login behavior, you can reduce the risk of <\/span><b>unauthorized access, data leakage<\/b><span style=\"font-weight: 400;\">, and <\/span><b>compliance violations<\/b><span style=\"font-weight: 400;\"> across your organization.<\/span><\/p>\n<h3><b>Want to strengthen Microsoft 365 access control with real-time monitoring and automation?<\/b><\/h3>\n<p><a href=\"https:\/\/www.itarian.com\/signup\/\"><b>Start your FREE Itarian trial now<\/b><\/a><span style=\"font-weight: 400;\"> and gain full visibility into identity-based threats, automate enforcement policies, and manage endpoint security across your enterprise.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Do you want to stop unauthorized access attempts from email addresses outside your trusted Microsoft 365 domain? If you&#8217;re asking, &#8220;how to block sign of non M365 emails,&#8221; you&#8217;re taking the right step toward securing your organization&#8217;s cloud environment. Whether you&#8217;re a cybersecurity professional monitoring identity threats or an IT manager responsible for user governance,&hellip; <span class=\"readmore\"><\/span><\/p>\n","protected":false},"author":11,"featured_media":12982,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-12972","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ticketing-system","entry"],"_links":{"self":[{"href":"https:\/\/www.itarian.com\/blog\/wp-json\/wp\/v2\/posts\/12972","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.itarian.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.itarian.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.itarian.com\/blog\/wp-json\/wp\/v2\/users\/11"}],"replies":[{"embeddable":true,"href":"https:\/\/www.itarian.com\/blog\/wp-json\/wp\/v2\/comments?post=12972"}],"version-history":[{"count":2,"href":"https:\/\/www.itarian.com\/blog\/wp-json\/wp\/v2\/posts\/12972\/revisions"}],"predecessor-version":[{"id":13132,"href":"https:\/\/www.itarian.com\/blog\/wp-json\/wp\/v2\/posts\/12972\/revisions\/13132"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.itarian.com\/blog\/wp-json\/wp\/v2\/media\/12982"}],"wp:attachment":[{"href":"https:\/\/www.itarian.com\/blog\/wp-json\/wp\/v2\/media?parent=12972"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.itarian.com\/blog\/wp-json\/wp\/v2\/categories?post=12972"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.itarian.com\/blog\/wp-json\/wp\/v2\/tags?post=12972"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}