Issues Deploying Microsoft.Web/sites/sourcecontrols With Github Continuous Deployment

**Bicep version**
0.15.31

**Describe the bug**
I am trying to deploy an Azure Functions App with a connection to a GitHub repo and git actions (git actions workflow file created through bicep). However, when I try to deploy this through a DevOps Pipeline I keep getting the following error: "Cannot find User with name {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx}." Unfortunately there is barely any information about this online and the official docs lack detail about how this works. The only thread with the same issue is [this GitHub Issue](https://github.com/Azure/azure-powershell/issues/2259) from 2016, but this error can be fixed by manually doing the CI/CD deployment through Azure portal UI.

Is there a way to run Microsoft.Web/sites/sourcecontrols specifically with a user identity through DevOps pipelines instead of a service principal? Or alternatively, is there a way to setup the azure functions app with a connection to GitHub by doing the authorization through de DevOps pipelines service principal (I assume not and I have no idea how that would work, but it would be a solution to this error based on the referenced thread and personal past experience with bicep / sourcecontrol).

**To Reproduce**
Steps to reproduce the behavior:
Run a sourcecontrol deployment through DevOps Pipelines.
```bicep
resource sourceControl 'Microsoft.Web/sites/sourcecontrols@2023-01-01' = {
parent: functionApp
name: 'web'
properties: {
repoUrl: funcAppGitRepoUrl
branch: funcAppGitRepoBranch
isManualIntegration: false
deploymentRollbackEnabled: false
isMercurial: false
isGitHubAction: true
gitHubActionConfiguration: {
generateWorkflowFile: true
isLinux: true
codeConfiguration: {
runtimeStack: 'PYTHON'
runtimeVersion: '3.9'
}
}
}
}
```

**Additional context**
Add any other context about the problem here.

Start with the Microsoft.Web/sites/sourcecontrols@2023-01-01 resource and the supplied Bicep reproduction, then compare deployment through an Azure DevOps pipeline with the portal flow described. Done means establishing whether a service principal can authorize the GitHub connection or documenting the supported identity/setup path, including the source of the “Cannot find User” error.

Written by the indexing model from the issue text.