<?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 Re: Clouds and Azure Classic Subscriptions - Prod and NonProd together in Cloud platforms</title>
    <link>https://community.dynatrace.com/t5/Cloud-platforms/Clouds-and-Azure-Classic-Subscriptions-Prod-and-NonProd-together/m-p/265072#M1877</link>
    <description>&lt;P&gt;Hey&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/83196"&gt;@dworks&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Looking into the docs for setting the integration up, it looks like the integration has been provided permissions for the prod subscription. As mentioned &lt;A href="https://docs.dynatrace.com/docs/shortlink/azure-monitoring-guide#azure-roles-and-permissions" target="_self"&gt;here&lt;/A&gt;, when setting up the permissions required you pick and choose the subscriptions. Further down, if you want to keep the permissions for both subscriptions you can also filter on tags. If this is not the case and the permissions specified when setting it up are correct, I'd recommend reaching out to support.&lt;/P&gt;</description>
    <pubDate>Thu, 12 Dec 2024 01:12:58 GMT</pubDate>
    <dc:creator>Fin_Ubels</dc:creator>
    <dc:date>2024-12-12T01:12:58Z</dc:date>
    <item>
      <title>Clouds and Azure Classic Subscriptions - Prod and NonProd together</title>
      <link>https://community.dynatrace.com/t5/Cloud-platforms/Clouds-and-Azure-Classic-Subscriptions-Prod-and-NonProd-together/m-p/265054#M1876</link>
      <description>&lt;P&gt;On our NonProd Dynatrace, we see both NonProd and Prod Azure subscriptions. That doesn't make any sense. We should only see our NonProd subscriptions. How do I screen out the Prod Azure subscriptions?&lt;/P&gt;</description>
      <pubDate>Wed, 11 Dec 2024 18:34:34 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Cloud-platforms/Clouds-and-Azure-Classic-Subscriptions-Prod-and-NonProd-together/m-p/265054#M1876</guid>
      <dc:creator>dworks</dc:creator>
      <dc:date>2024-12-11T18:34:34Z</dc:date>
    </item>
    <item>
      <title>Re: Clouds and Azure Classic Subscriptions - Prod and NonProd together</title>
      <link>https://community.dynatrace.com/t5/Cloud-platforms/Clouds-and-Azure-Classic-Subscriptions-Prod-and-NonProd-together/m-p/265072#M1877</link>
      <description>&lt;P&gt;Hey&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/83196"&gt;@dworks&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Looking into the docs for setting the integration up, it looks like the integration has been provided permissions for the prod subscription. As mentioned &lt;A href="https://docs.dynatrace.com/docs/shortlink/azure-monitoring-guide#azure-roles-and-permissions" target="_self"&gt;here&lt;/A&gt;, when setting up the permissions required you pick and choose the subscriptions. Further down, if you want to keep the permissions for both subscriptions you can also filter on tags. If this is not the case and the permissions specified when setting it up are correct, I'd recommend reaching out to support.&lt;/P&gt;</description>
      <pubDate>Thu, 12 Dec 2024 01:12:58 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Cloud-platforms/Clouds-and-Azure-Classic-Subscriptions-Prod-and-NonProd-together/m-p/265072#M1877</guid>
      <dc:creator>Fin_Ubels</dc:creator>
      <dc:date>2024-12-12T01:12:58Z</dc:date>
    </item>
    <item>
      <title>Re: Clouds and Azure Classic Subscriptions - Prod and NonProd together</title>
      <link>https://community.dynatrace.com/t5/Cloud-platforms/Clouds-and-Azure-Classic-Subscriptions-Prod-and-NonProd-together/m-p/265260#M1882</link>
      <description>&lt;P&gt;Following on from this, it seems the solution is to list our the subscriptions, then remove permissions from the Prod subscriptions. Then, in our Prod Dynatrace, to remove the permissions from the NonProd instances.&amp;nbsp;&lt;BR /&gt;The conclusion from that would be that this differentiation needs to be explicitly stated in the documentation for the setup of the connection.&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":smiling_face_with_sunglasses:"&gt;😎&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 13 Dec 2024 15:04:53 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Cloud-platforms/Clouds-and-Azure-Classic-Subscriptions-Prod-and-NonProd-together/m-p/265260#M1882</guid>
      <dc:creator>dworks</dc:creator>
      <dc:date>2024-12-13T15:04:53Z</dc:date>
    </item>
  </channel>
</rss>

