This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
{ | |
"$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#", | |
"contentVersion": "", | |
"parameters": { | |
"<parameter-name>" : { | |
"type" : "<type-of-parameter-value>", | |
"defaultValue": "<default-value-of-parameter>", | |
"allowedValues": [ "<array-of-allowed-values>" ], | |
"minValue": <minimum-value-for-int>, | |
"maxValue": <maximum-value-for-int>, |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
{ | |
"$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#", | |
"contentVersion": "1.0.0.0", | |
"parameters": {}, | |
"variables": {}, | |
"resources": [], | |
"outputs": {} | |
} |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Get-Command *json* | |
CommandType Name Version Source | |
----------- ---- ------- ------ | |
Cmdlet ConvertFrom-Json 3.1.0.0 Microsoft.PowerShell.Utility | |
Cmdlet ConvertTo-Json 3.1.0.0 Microsoft.PowerShell.Utility |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
{ | |
"servers":[ | |
{ | |
"server":"DC01", | |
"location":"Paris" | |
}, | |
{ | |
"server":"DC02", | |
"location":"London" | |
} |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
{ | |
"servers":[ "DC001", "ADFS001", "WAP001" ] | |
} |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
{ | |
"server":"DC001", | |
"location":"Paris" | |
} |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
{ "server":"DC001" } |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<# | |
This is an example on how to filter out users based on some standard filter and non-standard attribute. | |
In this case we pull all active users with the company Contoso, we force the attribute countryCode to be retrieved. | |
Then we select the users that have the countryCode empty and finally set the correct attributes for these users. | |
#> | |
$Users = Get-ADUser -Filter 'enabled -eq $true -and company -eq "Contoso"'` | |
-SearchBase "OU=Texas,DC=Contoso,DC=com"` | |
-Properties Department, Title, countryCode | ` | |
where {$_.countryCode -eq ""} | ` |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<# | |
Description: | |
This script modifies the existing Azure AD Directory Setting for Unified Groups with the objective to block users to create Office 365 Groups, and only allow users member of a dedicated security group. | |
Also it blocks external users to be added to Office 365 Groups (it's possible to by-pass this in applying a different setting to specific groups) and access Office 365 Groups. | |
It's recommended to run this script step by step PowerShell ISE. You can modify the settings or add others as you need. | |
Prerequisites: | |
- Install Azure Active Directory V2 PowerShell Module - Public Preview Release 2.0.0.114 from https://www.powershellgallery.com/packages/AzureADPreview/2.0.0.114 | |
- Create a security group in your Azure AD tenant or local synced AD for users allowed to create Office 365 Groups |
NewerOlder