<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Azure Datacenter Object in a Network Group in Firewall &amp; Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-Security-Management/Azure-Datacenter-Object-in-a-Network-Group/m-p/283085#M106984</link>
    <description>&lt;P&gt;Is this situation supported / best practice within R81.20&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We want to combine multiple Azure subnets "Data Center Objects" in 1 &lt;STRONG&gt;Network Group&lt;/STRONG&gt; as a destination.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So the situation is:&lt;/P&gt;&lt;P&gt;Source: EPG object (Cisco ACI)&lt;/P&gt;&lt;P&gt;Destination: &lt;STRONG&gt;Network Group (Containing Azure Subnets that are dynamic updated)&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Services: Service Group (Containing multiple services)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We're seeing that it don't hit the rule.&lt;/P&gt;&lt;P&gt;As soon as I change only the destination from "&lt;STRONG&gt;Network Group&lt;/STRONG&gt;" to a "&lt;STRONG&gt;Data Center Object of the Azure Subnet&lt;/STRONG&gt;" it works.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So are dynamic data center objects supported in a traditional network group?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 01 Oct 2026 07:35:55 GMT</pubDate>
    <dc:creator>RayP</dc:creator>
    <dc:date>2026-10-01T07:35:55Z</dc:date>
    <item>
      <title>Azure Datacenter Object in a Network Group</title>
      <link>https://community.checkpoint.com/t5/Firewall-Security-Management/Azure-Datacenter-Object-in-a-Network-Group/m-p/283085#M106984</link>
      <description>&lt;P&gt;Is this situation supported / best practice within R81.20&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We want to combine multiple Azure subnets "Data Center Objects" in 1 &lt;STRONG&gt;Network Group&lt;/STRONG&gt; as a destination.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So the situation is:&lt;/P&gt;&lt;P&gt;Source: EPG object (Cisco ACI)&lt;/P&gt;&lt;P&gt;Destination: &lt;STRONG&gt;Network Group (Containing Azure Subnets that are dynamic updated)&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Services: Service Group (Containing multiple services)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We're seeing that it don't hit the rule.&lt;/P&gt;&lt;P&gt;As soon as I change only the destination from "&lt;STRONG&gt;Network Group&lt;/STRONG&gt;" to a "&lt;STRONG&gt;Data Center Object of the Azure Subnet&lt;/STRONG&gt;" it works.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So are dynamic data center objects supported in a traditional network group?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 01 Oct 2026 07:35:55 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-Security-Management/Azure-Datacenter-Object-in-a-Network-Group/m-p/283085#M106984</guid>
      <dc:creator>RayP</dc:creator>
      <dc:date>2026-10-01T07:35:55Z</dc:date>
    </item>
    <item>
      <title>Re: Azure Datacenter Object in a Network Group</title>
      <link>https://community.checkpoint.com/t5/Firewall-Security-Management/Azure-Datacenter-Object-in-a-Network-Group/m-p/283105#M106995</link>
      <description>&lt;P&gt;Per &lt;A href="https://support.checkpoint.com/results/sk/sk167210" target="_self"&gt;sk167210&lt;/A&gt;, Data Center objects are not supported in Group objects.&lt;/P&gt;</description>
      <pubDate>Thu, 01 Oct 2026 15:13:45 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-Security-Management/Azure-Datacenter-Object-in-a-Network-Group/m-p/283105#M106995</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2026-10-01T15:13:45Z</dc:date>
    </item>
  </channel>
</rss>

