azure-docs | Open source documentation of Microsoft Azure | Azure library

I have an Azure Function (tried both Windows and Linux Consumption) using Azure App Service Authentication (Easy Auth) with a custom OpenId Connect provider to authenticate my Azure Function with an http trigger.

I configured a client in my Identity Provider (based on Duende Identity Server), acquired a token and then sent a request to the Azure Function (contains just the code that is initially created by Visual Studio when creating a Function App project).

This is the configuration I made in the Azure Portal:

When I now send the request to the Azure function endpoint I always get the following error:

We recently deployed azure event-hub java receiver/listener client by following azure-docs.

I truly believe arrays starts with 0, but that has nothing to do with this question. So anyways, I observed the following error raised from processError & also processPartitionClose

fellow engineers!

There is a need to transfer group owner from attribute "managedBy" (CN=%username%; part) of on-prem AD to Azure AD's "Owner" field of the same group (groups are synchronized, so it has same naming both in on-prem and Azure AD).

Issue is, that the process need to be automated, but there is not much options:

1. Module for AAD group management for PowerShell (but it doesn't work PowerShell ver7, because of .Net's core issue: https://github.com/MicrosoftDocs/azure-docs/issues/49896): https://docs.microsoft.com/en-us/azure/active-directory/enterprise-users/groups-settings-v2-cmdlets

2. Answer from another question on StackOverflow, but it doesn't seem to be my thing (because the need to deal with Extensions): How to add a Group Owner in Azure AD for the Group synced from on-premises active directory

3. Some kind of work-around with Graph API, but it isn't my choice too, since process need to be automated: https://social.msdn.microsoft.com/Forums/azure/en-US/4a293240-5ffc-45be-bd73-43f8868e5fab/graph-api-getting-quotmanaged-byquot-attribute-for-a-group-synced-with-azure-ad-connect?forum=WindowsAzureAD

So, maybe somebody stuck with same need or maybe could suggest a workaround with the PowerShell module, since there is not much of pleasure to go through more than 100 groups adding owners

Per an Azure Support response in an Azure Docs github issue (https://github.com/MicrosoftDocs/azure-docs/issues/75652), Consumption-tier Azure Functions on Linux don't support the General Settings tab

[I]t is by design that "General Setting" tab is not available for Linux Consumption function app.

Additionally, they don't support FTP or FTPS connections at all

When using the Consumption hosting plan, your function code and binding configuration files are stored in Azure File storage in the main storage account, not persistent file server. Actually it is not even possible to FTP to it. You will see /home folder is empty.

Finally, an Azure Advisor "High Impact" Security recommendation states

FTPS should be required in your function app

Given that there's no way to change it in the portal, how can you mitigate the recommendation?

I have a React SPA which uses msal. I have configured Azure AD as Identity Provider for my AADB2C. I can signIn/signOut and other operations.

If my user signs out off my application, I want to also sign out of my Identity Provider. I looked a bit into this matter 1, 2, 3, 4, 5.

At this moment, I use msal's logoutRedirect method.

We want to copy files from Google Storage to Azure Storage. We used following this guide: https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-google-cloud

We run this command:

I've followed the steps from https://docs.microsoft.com/en-us/azure/active-directory-b2c/saml-service-provider?tabs=windows&pivots=b2c-custom-policy

While testing receiving the error "Application registered corresponding to IssuerUri "">xyz.com/suite" in AuthRequest does not have assertion consumer service URL "">xyz.com/suite/saml/AssertionConsumer" specified in its metadata."

Using SAML tracer, I can see both my SAML Request and Response contains same AssertionConsumerServiceURL. MS document says: If you choose to configure the reply URL and logout URL in the application manifest without populating the application's metadata endpoint via the samlMetadataUrl property, Azure AD B2C will not validate the SAML request signature, nor will it encrypt the SAML response.

I can some workaround of specifying the PartnerEntity in the SP metadata URL for the Relying Party in the B2C_1A_signup_signin_saml custom policy. https://github.com/MicrosoftDocs/azure-docs/issues/61603

Unfortunately my web application security compliance does not allow to provide SP metadata endpoints. Do I need to host the SP / Appian SAML metadata file on Azure Storage account OR Is this mandatory to provide SP meta data endpoint to refer from Idp application registration manifest?

Second question, just want to make sure on the below. From MS Ref. doc: You can change the value of the IssuerUri metadata item in the SAML token issuer technical profile. This change will be reflected in the issuerUri attribute returned in the SAML response from Azure AD B2C. Your application should be configured to accept the same issuerUri during SAML response validation.

My question on the above paragraph, IssueUri example can be .onmicrosoft.com/c3bcfc1c-1234-4a3b-96e6-db0933071234 (application / client id) Is this correct?

Thanks.

An Azure Static Web App has a notion of auth that can be used to whitelist individual users, or individual identity providers (as in this question).

Is it possible to require authentication through the particular tenant/organizational directory used to set up the resource, through Azure configuration alone, as is currently possible with the ordinary Azure Web App Service; that is, require authentication through AAD as in the above linked question, but furthermore restrict access to members of the relevant tenant? If so, what might the corresponding routes.json look like?

See also this GitHub issue.

I've been trying to follow the direction here and applying it to nodejs.

I'm getting the following error: