Alaknar

joined 1 month ago
[–] Alaknar@sopuli.xyz -4 points 2 days ago (2 children)

~45% of men aren’t voting for the right, but they’re getting attacked for the actions of those that did. If anyone speaks up against that, they get mocked for dating to say “not all men”

Is this a US thing? Are things this fucked up over there?

[–] Alaknar@sopuli.xyz -2 points 1 week ago

The lock is there. The whole thing is encrypted.

If they somehow go through encryption, they won't just have the EU on their arses, governments of the entire world will be after them, because they trust that this encryption system makes their data secure.

[–] Alaknar@sopuli.xyz 12 points 1 week ago

While the book they put it all in is about 1500 years old.

[–] Alaknar@sopuli.xyz 23 points 1 week ago* (last edited 1 week ago) (1 children)

unconditional* love

* terms and conditions apply

 

cross-posted from: https://sopuli.xyz/post/30528273

Hi everyone!

Let's see if we can get put some live into this community! :)

I just started my journey with Azure Automation Accounts and Source Control and hit a snag. Couldn't find 100% certain information online, so hoping someone here might help.

We have an Automation Account that runs a bunch of Runbooks.

We have an Azure DevOps repo where I want all these Runbooks to live.

When setting up Source Control I need to Authenticate. From what I found out, in order to authenticate for automatic sync, the account used for authentication needs to be a Project Administrator with a Basic license on the Azure DevOps side, and have Contributor permissions on the Automation Account's side.

We have a Managed Identity set up with all those permissions.

Question: is it possible to use the Managed Identity for Authentication? When I click the "Authenticate" button, I get a regular interactive login page, and I can't switch to the MI. Do I need to spend two Basic licenses (one for MI, another for a Service Account) just to set up Source Control to Azure DevOps?

view more: next ›