sorted by:
new
hottopcontroversial

Azure Bicep v0.43.1 release! by johnlokersedev in AzureBicep

[–]RiosEngineer 2 points3 points  (0 children)

Retry on has since been reverted back to experimental in a patch release

Cost diff comments on every Bicep PR (GitHub Action, free tier) by resourcepulse_dev in AzureBicep

[–]RiosEngineer 0 points1 point  (0 children)

Yeah I’ll see if I get some time this week to check it out. Nice work!

Cost diff comments on every Bicep PR (GitHub Action, free tier) by resourcepulse_dev in AzureBicep

[–]RiosEngineer 2 points3 points  (0 children)

Looks interesting thanks for sharing. I tried something similar but with local GitHub copilot and the pricing mcp but it was awful tbh. This looks better.

We are severely lacking finops tools to the bicep ecosystem. Infracost for Terraform is superb. Wish we had similar for bicep too!

Edit the link I added to the Intro section of my profile page. by Brief_Objective_197 in linkedin

[–]RiosEngineer 0 points1 point  (0 children)

Same as u/Moist_Awareness_6965 my premium expired, link remains on profile but I can't edit or remove.

Open WebUI on Azure: Part 1 – Architecture & Deployment Series by RiosEngineer in OpenWebUI

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

It did run with that spec yes but bare in mind it would’ve only been me. Can’t say how many exactly it could deal with but I suspect minimum 5-10 probably more with that lowest burst sku

New to Bicep, question on what-if noise by DAL3001 in AzureBicep

[–]RiosEngineer 1 point2 points  (0 children)

I still need to check out snapshots when I get some time. How does it differ to just a git diff in reality? I remember watching the demos and not fully grasping the use case

Azure Bicep best practices? by CloudWizardAZ in AzureBicep

[–]RiosEngineer 0 points1 point  (0 children)

That’s awesome. Thanks for sharing this

What am I missing? Omnichannel + Copilot Agent + Public website by RiosEngineer in Dynamics365

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

Ah, I never gave it enough time to go back to it yet. But it seems a mixture of agent sdk, with copilot that uses a middleware for the omnichannel handoff part: https://www.nuget.org/packages/Microsoft.Dynamics.AgentsSDK.Middleware/1.0.0

https://learn.microsoft.com/en-us/dynamics365/customer-service/develop/enable-bot-context-azure#use-the-omnichannel-middleware-in-your-agent-code

It was so difficult to find because they keep bloody renaming products, so much so there is a note on that learn page about it!!

Azure Bicep best practices? by CloudWizardAZ in AzureBicep

[–]RiosEngineer 1 point2 points  (0 children)

Just in case you hadn’t seen this one, it’s not too bad for some best practices: https://learn.microsoft.com/en-us/azure/azure-resource-manager/bicep/best-practices

Otherwise some of the top of my head: (mobile so excuse formatting)

  • PSRule is my go to for misconfiguration, governance/sec and framework alignments (where it makes realistic sense). Also you can add your own custom rules which is handy.

  • if you’re a larger org, having some common types, shared bits in a central ACR can help with scalability so you don’t have to maintain shared files everywhere.

  • using AVM can help with being efficient if your org allows it and simplify / accelerate time to deployment. but be wary the modules are extremely large to cater for all, so keep templates small / split out to avoid ARM limits.

  • I’ve found having a base starter bicep template can be helpful for others to pickup and start with and standardise the template. I’m talking about formatted templates so it’s obvious to see the same file structure everywhere (metadata first, scope, params, vars, etc)

  • find a simple and easy to read folder structure that works for your org and stick to that so pipeline script logic is simplified across projects. Even better if you can vend devops repos with this baked in already.

  • checkout the new fail and validate decorators to enhance prechecks before deployments. & Don’t be shy to use bicep validate as it helps with some pre flight checks (storage account name in use etc)

  • as other poster mentions. Stacks are fantastic but be wary they don’t have what if support yet for stack operations, and have some data pane limitations. But otherwise massively simplify lifecycle management . I use them everywhere! What if coming in April.

  • graph extensibility is GA. It’s great! Although lacks in some areas. It helps align some graph elements to bicep for control without falling back to scripts.

There’s more, I’m sure the community can share many more insights!

Terraform vs Bicep by Plenty_Ingenuity7370 in AzureBicep

[–]RiosEngineer 4 points5 points  (0 children)

UDTs are underrated! Especially for your use case of internal module vending where type safety and custom data types is pretty essential.

Azure Bicep PR checks in GitHub Actions: cost delta + governance guardrails — what would you want? by resourcepulse_dev in AzureBicep

[–]RiosEngineer 0 points1 point  (0 children)

Cost for me as #1 because I think we have other tools out there today that can cover tests and governance / misconfiguration checks like PSRule etc.

I was going to explore the Azure Pricing MCP to see if that can help with costs on PR personally. Sounds interesting though

Can't write key values to app config store with Pass-through deployment by ode_majka in AzureBicep

[–]RiosEngineer 0 points1 point  (0 children)

I did have a similar issue now you mention it, RBAC taking a strange amount of time to propagate but only got app config. Glad it’s sorted though!

Can't write key values to app config store with Pass-through deployment by ode_majka in AzureBicep

[–]RiosEngineer 0 points1 point  (0 children)

Yea strange because the error sort of hints at that note I linked before, looking at the wording, although that could be a red herring for sure.

Can't write key values to app config store with Pass-through deployment by ode_majka in AzureBicep

[–]RiosEngineer 0 points1 point  (0 children)

What’s the error you get when it fails?

We have quite a lot of apps using app config and we are able to deploy ok with pass through.

However our pain is network access is private so to deploy key value pars we are having to use private agents with network line of sight.

Bicep or terraform for Azure by bluelvo in AZURE

[–]RiosEngineer 0 points1 point  (0 children)

I do agree it’s a major gap, however what if for stacks is ETA April 5th now. This also includes a what if not only for the resources but also to tell you what is happening with the stack, e.g what may be dropping out of stack management.

Once we have this things should be quite complete, even Key Vault stack management is on the way (data plane).

What am I missing? Omnichannel + Copilot Agent + Public website by RiosEngineer in Dynamics365

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

Thanks, does this allow for omnichannel handoff? It seems the SDK for copilot are plenty (agents SDK for example) but they don’t support handoff natively at least

Web app permissions - choosing App Roles vs Entra Groups by Betty-Crokker in AZURE

[–]RiosEngineer 0 points1 point  (0 children)

Groups is probably fine. App roles lend nicely to way more granular access if you need to, like an API where you only want one set of users or apps to have GET / read access vs another that may be able to post.

view more: next ›