Enterprise-Scale
Azure PowerShell
Our great sponsors
Enterprise-Scale | Azure PowerShell | |
---|---|---|
19 | 15 | |
1,609 | 4,068 | |
2.5% | 1.8% | |
8.7 | 9.9 | |
8 days ago | 5 days ago | |
PowerShell | C# | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Enterprise-Scale
- Azure Policies
-
App Gateway deploy diagnostic settings with Azure Policy
We are deploying all our App Gateways in the hub subscription (a hub and spoke architecture). Occasionally, App Gateways are created without the diagnostic settings enabled on them (I know, this can be automated with IaC, but there more to it on a org level, and not worth discussing here, but yes, this could be a solution). However, I’m planning to use the following policy definition provided by the Azure Enterprise Scale project https://github.com/Azure/Enterprise-Scale/blob/main/src/resources/Microsoft.Authorization/policyDefinitions/Deploy-Diagnostics-ApplicationGateway.json I’ve imported it, tested, works. BUT, as of today all App Gateways are sitting in one resource group, meaning that when app/dev teams want to access the logs, they get to potentially view logs for others as well (different teams, countries etc.). Not sure how this could be a problem from a regulatory, compliance standpoint, but the IT team was thinking about splitting the App Gateways per individual resource groups scope to the countries (one rsg for country x, another for country y …) where people from subscription x would be granted access to only rsg x within the transit subscription. Each would then have a dedicated Log analytics workspace in that resource group (the central IT team would still have access to all logs, countries only scope with RBAC to the respective resource groups). I could then of course assign per resource group the above policy n-time to make sure that the parameters reflected in each policy assignment point to the correct Log Analytics workspace.
-
Recommended Azure Policies
Hey! You should check out all the policies that are included within the Azure landing zone, these are what’s recommended as part of a landing zone deployment: https://github.com/Azure/Enterprise-Scale/wiki/ALZ-Policies
-
Management group separation
And it is in separate MG in the reference Enterprise Scale but if you look at the policies assignments - https://github.com/Azure/Enterprise-Scale/wiki/ALZ-Policies - you will notice policies I mentioned are assigned at the intermediate root level, so sandbox MG inhertis them.
-
dis-allow users to add inbound port rules?
There is a Azure policy somewhere in https://github.com/Azure/Enterprise-Scale that can block creation of rules for specific ports, etc.
-
[Issue] No cost analysis when scoping to management group
If you plan to scale out more (and for many other reasons), you should consider the reference architecture for Azure Landing Zones fka Enterprise Scale Landing Zones. https://github.com/Azure/Enterprise-Scale
-
Management group structure for enterprise environment?
There is also a terraform version if that is your preferred IaC - https://github.com/Azure/Enterprise-Scale
-
Azure Landing Zone / Enterprise Model Assistance
You can opt to deploy the ESLZ reference implementation for AdventureWorks and select the single option for platform. https://github.com/Azure/Enterprise-Scale/
-
Azure Policy to Audit Application Gateway SSL Policy?
{ policyType: "Custom", mode: "Indexed", displayName: "Application Gateway should be deployed with proper sslPolicy", description: "This policy enables you to restrict that Application Gateways is always deployed with the proper sslPolicy", metadata: { version: "1.0.0", category: "Network", source: "https://github.com/Azure/Enterprise-Scale/" }, parameters: { effect: { type: "String", allowedValues: [ "Audit", "Deny", "Disabled" ], defaultValue: "Audit", metadata: { displayName: "Effect", description: "Enable or disable the execution of the policy" } } }, policyRule: { if: { allOf: [ { field: "type", equals: "Microsoft.Network/applicationGateways" }, { field: "Microsoft.Network/applicationGateways/sslPolicy.policyName", notequals: "20170401S" } ] }, then: { effect: "[parameters('effect')]" } } }
-
MSDN / no global owner rights
I have a MSDN subscription but do not have Owner rights to it. Is there a work around so I deploy an ARM template from the /Azure/Enterprise-Scale github repo.? https://github.com/Azure/Enterprise-Scale
Azure PowerShell
-
How to return release date when using Find-Package
Author : Microsoft Corporation CompanyName : azure-sdk Copyright : Microsoft Corporation. All rights reserved. PublishedDate : 23-May-23 04:37:01 InstalledDate : UpdatedDate : LicenseUri : https://aka.ms/azps-license ProjectUri : https://github.com/Azure/azure-powershell #>
-
resources connected to log analytics workspace
Get-AzOperationalInsightsDataSource
-
Microsoft Graph Endpoint vs Az endpoints (not AzureAD)
https://github.com/Azure/azure-powershell/issues/14568 looks like the Az cmdlets use the Azure Graph so likely they die as well. Would be nice if they would document that.
-
Azure Cloud Shell help more info in comments
Since the first error is the write-warning from connect-azaccount (see GitHub) and the second is a cmdlet in that same module.
- ForEach-Object Scoping and Runspace issues
- Using Azure CLI/PowerShell to add a diagnostic setting
-
Az PowerShell v7 is out today
Downloads over here: https://github.com/Azure/azure-powershell/releases
- How do I Import-AzAutomationRunbook a 7.1 runtime version powershell runbook?
-
Book recommendation for PowerShell programming needed (programming API, PS modules, scripts embedded in C# applications )
You might also want to have a look at the source for some PowerShell modules, for example https://github.com/Azure/azure-powershell/
-
How to fix "ERROR: Parameter 'Disk.location' can not be None."
https://docs.microsoft.com/en-us/azure-stack/aks-hci/container-storage-interface-disks
What are some alternatives?
terraform-azurerm-caf-enterprise-scale - Azure landing zones Terraform module
Octokit.NET - A GitHub API client library for .NET
ALZ-Bicep - This repository contains the Azure Landing Zones (ALZ) Bicep modules that help deliver and deploy the Azure Landing Zone conceptual architecture in a modular approach. https://aka.ms/alz/docs
AWS SDK - The official AWS SDK for .NET. For more information on the AWS SDK for .NET, see our web site:
azure-quickstart-templates - Azure Quickstart Templates
Bot Builder SDK - Bot Framework provides the most comprehensive experience for building conversation applications.
opnazure - This template allows you to deploy an OPNsense Firewall Azure VM using the opnsense-bootsrtap installation method
Getty Images API SDK - Getty Images API SDK - .NET
TailwindTraders
DropNet - Client Library for the Dropbox API
CloudAdoptionFramework - Code samples and extended documentation to support the guidance provided in the Microsoft Cloud Adoption Framework
Dropbox.NET - The Official Dropbox API V2 SDK for .NET