Unable to enable autosync option under sourcecontrol in Azure Automation

VinodKumar-0434 321

Hi All,

I'm trying to set up source control for Azure automation account, but when I click EnableAutoSync I'm seeing below error.

An error occurred while updating the source control named 'SCReposGit'. Error details: SourceControl autoSync setup failed for 'SCReposGit'..

I'm the project administrator on the DevOps organization and I also have enabled Third-Party application access via OAuth. I have also added the system defined identity as a contributor on the automation account.

Did I miss anything to make it work?

Tiago Utz Foscarini 10 Reputation points

2024-05-30T20:46:56.49+00:00

Noticed the same thing happening this week.

Already did the same process for different accounts before with no issue, now it does not work for any resource. Existing or new.

Tried through Portal and through Powershell.

2 answers

Deepanshukatara-6769 10,690 Reputation points

2024-05-24T08:29:29.17+00:00

Hi Vinod,

I think we need to enable the 'Third-party application access via OAuth' in Azure DevOps / Organization Settings / Policies / Application connection policies

Apparently this policy is 'defaulted to off for all new organizations.'

https://learn.microsoft.com/en-us/azure/devops/organizations/accounts/change-application-access-policies?view=azure-devops#application-connection-policies

Also , As per this Azure docs github issue, this Azure document is now updated with the details around the same , please check this

Kindly accept answer , if it helps, Thanks!
Please sign in to rate this answer.
VinodKumar-0434 321 Reputation points

2024-05-24T08:33:02.9033333+00:00

I have enabled it already, still same exception

Deepanshukatara-6769 10,690 Reputation points

2024-05-24T08:40:05.7033333+00:00

Have you ensure that the Personal Access Token (PAT) you're using has the correct scopes for Azure Automation integration with Azure DevOps (Git):

Code (Read & Write)

Service Connections (Read & Manage)

VinodKumar-0434 321 Reputation points

2024-05-24T08:46:10.7333333+00:00

Given full access

Deepanshukatara-6769 10,690 Reputation points

2024-05-24T09:20:10.0133333+00:00

Ok if all seems ok , one more check I think you are not using private link in networking of automation account , right?

if yes then I would suggest opening a Support Ticket so that it can be investigated 1:1 with backend logs (if required).

Deepanshukatara-6769 10,690 Reputation points

2024-05-27T05:25:47.9233333+00:00

@vinod , can you please update on this did you got chance to raise support ticket or issue got resolved?

Tiago Utz Foscarini 10 Reputation points

2024-05-30T20:49:39.2466667+00:00

Can confirm that for me the Automation Account AutoSync is still not working, even without Private Endpoint and public Access enabled.

Deepanshukatara-6769 10,690 Reputation points

2024-05-31T06:19:05.8566667+00:00

Ok @tiago thanks for your input and confirmation , @vinod as mentioned by us in previous regarding private link , could you please check the same for your issue , if it could help by anyway , please update us , Thanks!

VinodKumar-0434 321 Reputation points

2024-05-31T06:42:06.8333333+00:00

@Deepanshukatara-6769 I don't have private link or network configs around automation account. I'm the project admin on the azure DevOps project as well. Seems like it is an issue for most of the people. Can you try to replicate the same at your end once and check.

B/w I have followed the doc and did all the mentioned points. But no luck with portal and powershell.

Deepanshukatara-6769 10,690 Reputation points

2024-05-31T12:34:59.81+00:00

Ok sure Vinod let me try and get back to you on this

VinodKumar-0434 321 Reputation points

2024-06-04T08:30:57.6533333+00:00

@Deepanshukatara-6769 Have you tried?

Julien BARREAU-MAINSON 41 Reputation points

2024-06-04T13:50:03.18+00:00

I'm getting the exact same issue than @Tiago Utz Foscarini

mourad rahma 1 Reputation point

2024-06-04T17:13:40.3433333+00:00

Facing the same issue,

Deepanshukatara-6769 10,690 Reputation points

2024-06-05T06:00:55.68+00:00

@vinod/All, I tried and I am also getting same error it seems some bug from Azure end , I would inform concern azure product engineering team on this and look for the resolution on this , will keep you posted on this .

If it is something urgent, you can raise support ticket in portal

Thanks

Deepanshu

Kamil Janiec 5 Reputation points

2024-06-05T11:34:31.9466667+00:00

Any news? having same issue.

Isaac Vergara 0 Reputation points

2024-06-05T15:26:28.13+00:00

Having the same issue as you do. Did try to create it through Portal and PS with a full access PAT.

Having conversations with MS support. Will let you know if we find out something.

Julien BARREAU-MAINSON 41 Reputation points

2024-06-05T15:48:12.11+00:00

Tried both Oauth and PAT, though both are failing.

There's something wrong with autosync feature...

Tiago Utz Foscarini 10 Reputation points

2024-06-06T17:09:03.81+00:00

Yeah, today I tried to remove a source control from a different account that had auto sync, and you can't even Delete one with it enabled:

Delete source control failed.

An error occurred while deleting the source control named 'DevOps'.

Error details:

SourceControl autoSync setup failed for 'DevOps'..

Kamil Janiec 5 Reputation points

2024-06-07T05:36:02.6633333+00:00

that is a response I got from MSFT after 3 days of investigation:

We understand the urgency of the issue and are committed towards delivering a solution to you at the earliest. However, at this time we do not have any update that we can share with you but we can assure you the investigation is on track and I am keenly following up with my Product group team for updates.

VinodKumar-0434 321 Reputation points

2024-06-11T15:20:03.6166667+00:00

@Kamil Janiec any response from MS

Tiago Utz Foscarini 10 Reputation points

2024-06-11T20:00:30.73+00:00

I have just tried again today and it worked fine. Seems like it has been resolved.

Kamil Janiec 5 Reputation points

2024-06-12T05:37:30.7366667+00:00

For me it worked as well. No explanation from msft though.

Julien BARREAU-MAINSON 41 Reputation points

2024-06-13T15:23:30.23+00:00

I don't think it's fully resolved : autosync is working again for existing source controls, though new ones either fail or create new runbook in "New" state without the possibility to publish/start the runbook. Status is stuck in "New" state.

Julien BARREAU-MAINSON 41 Reputation points

2024-06-13T15:26:22.5366667+00:00

I don't think the issue is fully resolved : autosync feature is working again for existing source controls, though new source control either failed to create runbook OR the runbook are stuck in "New" status without any possibility to publish/start them...

Julien BARREAU-MAINSON 41 Reputation points

2024-06-17T11:51:51.8133333+00:00

The autosync issue is back ...

Isaac Vergara 0 Reputation points

2024-07-02T12:06:12.5633333+00:00

Suddently it started working on my end. It seems like a problem from MS.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Nelson Enrique Polo Igirio 0 Reputation points

2024-06-07T20:02:32.25+00:00

Hello, I have the same issue: An error occurred while updating the source control named 'GitHub1'. Error details: SourceControl autoSync setup failed for 'GitHub'.

Problems with GitHub and also Azure DevOps. It was working a month ago.

If you need any further assistance, feel free to ask!
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Unable to enable autosync option under sourcecontrol in Azure Automation

2 answers

Your answer