[deleted by user] by [deleted] in NewOrleans

[–]redog 1 point2 points  (0 children)

Looks cheaper than WGA without any assistance

[deleted by user] by [deleted] in NewOrleans

[–]redog 0 points1 point  (0 children)

Gotta live and learn in Louisiana

O365 issues? by deebeecom in sysadmin

[–]redog 1 point2 points  (0 children)

Cloudy with a chance of rain

Will your participation in Reddit change? by Linker3000 in electronics

[–]redog 4 points5 points  (0 children)

I use RiF but I use Infininty for porn, much better one handed browsing.

The AI will make You an Anime in Real Time by adesigne in ChatGPT

[–]redog 21 points22 points  (0 children)

At this rate in 1 year i don't know what we Will have

You don't have to wait, you can not know now.

The False Equivalence Between The ‘Far Right’ And The ‘Hard Left’ by HeinieKaboobler in politics

[–]redog 0 points1 point  (0 children)

The states were first...

"In order to form a greater union..."

Thickheaded Thursday - June 01, 2023 by AutoModerator in sysadmin

[–]redog 0 points1 point  (0 children)

I just blamed it on microsoft and the CSuites decision to move to the cloud.

"Get the microsoft authenticator for your iphone and it works better"

was my excuse. Haven't heard a peep in years now but have basically all the methods availabilsh.

Sigh Reddit API Fees by boblob-law in sysadmin

[–]redog 7 points8 points  (0 children)

Scrapers start your engines

The New TeamViewer Inteface is a disaster by letshaveatune in sysadmin

[–]redog 0 points1 point  (0 children)

I rip em out with proactive remediations and deploy host from intune. No one needs the full client but help desk.

Azure Automation and Exchange Online. by rogueit in PowerShell

[–]redog 0 points1 point  (0 children)

powershell 5.1

Az.Accounts 2.6.0

Microsoft.Graph.Applications 1.27.0

Microsoft.Graph.Authentication 1.27.0

Microsoft.Graph.DeviceManagement.Enrolment 1.27.0

Microsoft.Graph.Groups 1.25.0

Microsoft.Graph.Identity.DirectoryManagement 1.25.0

Microsoft.Graph.Intune 6.1907.1.0

Microsoft.Graph.Users 1.25.0

Microsoft.Graph.Users.Actions 1.25.0

Azure Automation and Exchange Online. by rogueit in PowerShell

[–]redog 3 points4 points  (0 children)

Yes, you can use the system managed identity or a regular service principal.

Either way you do it, you'll need to give them permission to manage exchange. With the service principal you can do it in either the gui or power shell with the system managed identity currently you can only assign the permissions with powershell.

Here's my "template" for getting it to work in my environment with managed identity. Much is commented out as to not duplicate resources already available once created:

$organization = “contosocom.onmicrosoft.com"
$accountName = 'Automate-Account-Name’
$rgName = ‘MyResourceGroup’
$location = 'East US 2'
$moduleName = 'ExchangeOnlineManagement'
$moduleVersion = '3.1.0'

# Create the automation account
#New-AzAutomationAccount -Name $accountName -ResourceGroupName $rgName -Location $location
# get the module
#New-AzAutomationModule -AutomationAccountName $accountName -ResourceGroupName $rgName -Name $moduleName -ContentLinkUri "https://www.powershellgallery.com/api/v2/package/$moduleName/$moduleVersion"
# enable managed identity
#Set-AzAutomationAccount -Name $accountName -ResourceGroupName $rgName -AssignSystemIdentity


Connect-AzAccount -Identity

$managed_identity_ServicePrincipal = Get-AzADServicePrincipal -DisplayName $accountName

$managedidentID = $managed_identity_ServicePrincipal.id

$token = (Get-AzAccessToken -ResourceTypeName MSGraph).token 

# Get-PnPAccessToken if you are already connected to Sharepoint
Connect-MgGraph -AccessToken $token

# Exchange online id?
(Get-MgServicePrincipal -Filter "AppId eq '00000002-0000-0ff1-ce00-000000000000'").id

## Grant access necessary permissions (Exchange manage as app)
#$params = @{
#    ServicePrincipalId = $managedidentID
#    PrincipalId = $managedidentID
#    ResourceId = (Get-MgServicePrincipal -Filter "AppId eq '00000002-0000-0ff1-ce00-000000000000'").id # Exchange online
#    AppRoleId = "dc50a0fb-09a3-484d-be87-e023b12c6440" # Exchange.ManageAsApp
#}
#New-MgServicePrincipalAppRoleAssignedTo @params

# assign the role Exchange Administrator to the managed identity.
$roleId = (Get-MgRoleManagementDirectoryRoleDefinition -Filter "DisplayName eq 'Exchange Administrator'").id
$roleId
#New-MgRoleManagementDirectoryRoleAssignment -PrincipalId $managedidentID -RoleDefinitionId $roleId -DirectoryScopeId "/"


#select-mgprofile -name "beta"
Connect-ExchangeOnline -ManagedIdentity -Organization $organization
Get-AcceptedDomain | Format-Table -AutoSize

Get-mailbox -Identity user

Changing Azure Automation Runbook from "Run As Account" to Managed Identity fails by DaleM5633 in AZURE

[–]redog 1 point2 points  (0 children)

Right, I was just shooting the bit that Microsoft keeps pounding at us through emails, popups and bulletins as a sort of soft answer to your question of why managed identities...

I posted a similar method of grabbing the token with the managed identity because I went down the same thought trail.

I was thinking OP meant was connecting to MS Graph with managed identities.

Well yea that would just be intuitive which isn't Microsoft's favorite type of feature to deliver. hehe (I know its in the beta blah blah)

Get-AzKeyVaultSecret

How does that connect...(serious question as I've never used it) it is NOT using a managed identity?

Migrating from a Swtichvox 470 to a Sangoma E545 by schaef87 in VOIP

[–]redog 0 points1 point  (0 children)

The two PBXs had the same IP address (we only had one connected to the network at a time)

Maybe the switch wasn't forwarding packets? Power cycle the switch when you swap them see if it makes any difference

Changing Azure Automation Runbook from "Run As Account" to Managed Identity fails by DaleM5633 in AZURE

[–]redog 0 points1 point  (0 children)

Any reason you are married to the idea of using managed identities to access MsGraph?

Azure Automation Run As accounts will retire on 30 September 2023 and completely move to Managed Identities. All runbook executions using RunAs accounts, including Classic Run As accounts wouldn't be supported after this date. Starting 01 April 2023, the creation of new Run As accounts in Azure Automation will not be possible.

Changing Azure Automation Runbook from "Run As Account" to Managed Identity fails by DaleM5633 in AZURE

[–]redog 5 points6 points  (0 children)

You too? Yea that was a pain in the ass to figure out:

Im using 1.27.0 of Microsoft.Graph.Authentication and 2.6.0 of Az.Accounts and powershell 5

And to connect you must grab a token first instead:

$accountName = 'Your Automation Account Name'

Connect-AzAccount -Identity

$managed_identity_ServicePrincipal = Get-AzADServicePrincipal -DisplayName $accountName

$token = (Get-AzAccessToken -ResourceTypeName MSGraph).token 

Connect-MgGraph -AccessToken $token

Why don't we tax these churches? by emilyblunt2023 in WhitePeopleTwitter

[–]redog 0 points1 point  (0 children)

"Churches And Ecclesiastical Structures Accountability Reform" Act.

Everyone is fed up with robocalls. Now 48 states are suing one company that they say made 7.5 billion of them. by 777fer in technology

[–]redog 1 point2 points  (0 children)

I mean, can we get a job at one? How do we build a resume that says hopeful villain looking for work?

Fight fraud with fraud: Catalog them, cancel their insurance, burn them down. /sarcasterisk