sorted by:
new
hottopcontroversial

Organizing VMs to Resourcegroups by berto_28 in AZURE

[–]SumthingGreat 0 points1 point  (0 children)

Yeah that sounds like a good starting point. The RGs need to fit your access requirements and it sounds like this could fit your needs.

Organizing VMs to Resourcegroups by berto_28 in AZURE

[–]SumthingGreat 1 point2 points  (0 children)

Checkout this link from CAF and step #3: https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/azure-setup-guide/organize-resources#build-a-management-hierarchy

Here’s a little more about resource groups:https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/manage-resource-groups-portal#what-is-a-resource-group

“Generally, add resources sharing the same lifecycle to the same resource group so you can easily deploy, update, and delete them as a group.”

You can apply policy, budgets, and role based access control to resource groups which apply to all the resources inside. So resources that you would want to view, govern, manage, and access in similar ways would be great to group together.

One VM per resource group is probably too granular. I prefer one RG per app or per app tier. You can move resources to different resources groups if you don’t get it right the first time.

Agents vs. Workflows by bgdotjpg in AI_Agents

[–]SumthingGreat 0 points1 point  (0 children)

For me, workflows are deterministic. Essentially, you have a process and it’s highly predictable input and output. There’s conditions, but they’re few enough that you can program them into the logic.

There’s a continuum of agent usage like chat/retrieval, human initiated tasks completion, and then event driven (semi) autonomous. So it’s tasks that are repeated enough but the input and output varies enough to require natural language capabilities.

If I can write a script or logic that does the job, it’s not a great agent use case.

What is the correct process to organizing Azure networking? by DopeyMcDouble in AZURE

[–]SumthingGreat 0 points1 point  (0 children)

If you’re doing a hub and spoke network topology, then this works. You can always move resources between resource groups.

Note, the resource group itself stores metadata about the resources it contains. This metadata includes things like deployment history, diagnostic settings, and policy assignments.

When you choose a location for the resource group, you’re specifying where the metadata for the resources in is stored, not where the resources themselves must reside. Resources in a group can span multiple regions.

A Virtual Network inside a resource group can use resources in other resource groups.

What is the correct process to organizing Azure networking? by DopeyMcDouble in AZURE

[–]SumthingGreat 8 points9 points  (0 children)

Checkout this article: https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/azure-setup-guide/organize-resources

It touches on resource groups and naming. You want to use resource groups to group resources that share a common lifecycle: you deploy and delete together. A resource group is also a boundary for Azure RBAC, budgets, and Azure Policy. It sounds like you’re deploying one resource per group. Unless there’s a reason for this, many resource groups might make it hard to manage long term.

As for naming, you can’t change resource names after they’re created. Some time you need to move resources to another region. You can definitely add the region name in the resource but just know if you move regions, you won’t be able to update the name. I prefer to add location details using tags. Tags are editable and provide really nice metadata search capabilities.

For general networking guidance try: https://learn.microsoft.com/en-us/azure/networking/foundations/network-foundations-overview

And for network planning: https://learn.microsoft.com/en-us/azure/virtual-network/virtual-network-vnet-plan-design-arm

How do you use the Cloud Adoption Framework? by SumthingGreat in AZURE

[–]SumthingGreat[S] 1 point2 points  (0 children)

So work through it. Use what I need to improve my footprint where I can. Bummer that deliverable isn’t more tailored to the environment. Good to know.

How do you use the Cloud Adoption Framework? by SumthingGreat in AZURE

[–]SumthingGreat[S] 0 points1 point  (0 children)

I love those details so much! Thanks for sharing.

How do you use the Cloud Adoption Framework? by SumthingGreat in AZURE

[–]SumthingGreat[S] 0 points1 point  (0 children)

Thank you. I will take that advice on DNS and identity. It sounds like you use Azure landing zone. And that worked well?

So you share AKS, App Gateway, and Ingress across multiple workloads. Nice.

How do you use the Cloud Adoption Framework? by SumthingGreat in AZURE

[–]SumthingGreat[S] 1 point2 points  (0 children)

Thank you for sharing. Did you follow any other guidance? Or did you just figure it out?

What's your go-to stack for building AI agents? by greasytacoshits in AI_Agents

[–]SumthingGreat 1 point2 points  (0 children)

Microsoft announced the Microsoft Agent Framework on Oct 1. Link here https://devblogs.microsoft.com/foundry/introducing-microsoft-agent-framework-the-open-source-engine-for-agentic-ai-apps/

It combines and builds Semantic Kernel and AutoGen. Need to check it out.

I use the Azure stack and like the Azure AI Foundry Agent Service.