<?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 Prisma Access CloudBlade to Native Integration experience in Prisma SD-WAN CloudBlades Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/prisma-sd-wan-cloudblades/prisma-access-cloudblade-to-native-integration-experience/m-p/1225548#M8</link>
    <description>&lt;P&gt;With native integration now part of SCM for creating tunnels to Prisma Access from IONs, we were looking to rid ourselves of the beast that is the Prisma Access CloudBlade (though admittedly it's improved a fair bit the last couple of years, not nearly as painful as it used to be).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I know we need to coordinate with TAC to turn down the CloudBlade and enable the native integration functionality, but I was wondering if anyone has actually done it and what their experience was in terms of complexity, outage time, unforseen roadblocks, ability to stage changes, partial cutovers, etc.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We have 100+ tunnels across all timezones and lots of 24/7 operations, so we don't really have a time where an extended outage isn't going to be impactful, so getting a handle on what to expect in reality, rather than the TAC sanitised version, would be great.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Cheers&lt;/P&gt;</description>
    <pubDate>Thu, 03 Apr 2025 07:57:46 GMT</pubDate>
    <dc:creator>James.McCutcheon</dc:creator>
    <dc:date>2025-04-03T07:57:46Z</dc:date>
    <item>
      <title>Prisma Access CloudBlade to Native Integration experience</title>
      <link>https://live.paloaltonetworks.com/t5/prisma-sd-wan-cloudblades/prisma-access-cloudblade-to-native-integration-experience/m-p/1225548#M8</link>
      <description>&lt;P&gt;With native integration now part of SCM for creating tunnels to Prisma Access from IONs, we were looking to rid ourselves of the beast that is the Prisma Access CloudBlade (though admittedly it's improved a fair bit the last couple of years, not nearly as painful as it used to be).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I know we need to coordinate with TAC to turn down the CloudBlade and enable the native integration functionality, but I was wondering if anyone has actually done it and what their experience was in terms of complexity, outage time, unforseen roadblocks, ability to stage changes, partial cutovers, etc.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We have 100+ tunnels across all timezones and lots of 24/7 operations, so we don't really have a time where an extended outage isn't going to be impactful, so getting a handle on what to expect in reality, rather than the TAC sanitised version, would be great.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Cheers&lt;/P&gt;</description>
      <pubDate>Thu, 03 Apr 2025 07:57:46 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/prisma-sd-wan-cloudblades/prisma-access-cloudblade-to-native-integration-experience/m-p/1225548#M8</guid>
      <dc:creator>James.McCutcheon</dc:creator>
      <dc:date>2025-04-03T07:57:46Z</dc:date>
    </item>
  </channel>
</rss>

