Enable Azure AD Login in Azure APIM new developer portal - azure

Any idea how to enable Azure Login in new developer portal? I have tried below link to set up account on azure AD. It enabled AD login in old developer portal but not in new one
https://learn.microsoft.com/en-us/azure/api-management/api-management-howto-aad
Any link which can help with this?

This feature has not been released on Azure APIM new developer portal yet. Details see here .
As APIM product team indicated , this feature is comming soon :
it will be completed by general availability release, which is planned
for October/November.
Hope it helps.

Now Its enabled. I was able to configure to azureAD sign in.
Note: To Auto populate Sign up page. need to add additional claim (email) in the Azure AD App.
can follow below link
https://learn.microsoft.com/en-us/answers/questions/145976/can-sign-up-page-be-auto-populated-after-aad-authe.html

Related

Azure API Management new dev portal - how to add a new administrator

There is a step by step configuration to add API Management Administrators and then use a Powershell command to retrieve a URL to open the Developer portal as an administrator (https://learn.microsoft.com/en-us/azure/api-management/api-management-faq#how-do-i-add-a-user-to-the-administrators-group).
But unfortunately, it is not working with the new developer portal, only with the legacy portal.
What are the steps to use with the new developer portal?
It's a bit more involved.
Generate yourself a token using this API: https://learn.microsoft.com/en-us/rest/api/apimanagement/2019-01-01/user/getsharedaccesstoken
Get service details using this API: https://learn.microsoft.com/en-us/rest/api/apimanagement/2019-01-01/apimanagementservice/get to see if new dev portal has been assigned custom hostname. Can skip it if you already have this information from somewhere else.
You redirect URL will be: https://[hostname]/signin-sso?token=[token]

Not Getting option to change to manual SCIM Provisioning

How I can change the option of scim provisioning from automatic to manual in Azure ?
It is enabled only when there is no automatic Azure AD provision connector available
Manual provisioning means there is no automatic Azure AD provisioning
connector for the app yet. User accounts must be created manually, for
example by adding users directly into the app's administrative portal,
or uploading a spreadsheet with user account detail. Consult the
documentation provided by the app, or contact the app developer to
determine what mechanisms are available.

Azure AD B2C Custom Domain

There does not seem to be an option to set up a custom domain for Azure AD B2C. With Azure AD it was available. The B2C version has a side help panel which indicates custom domains can be used, but no indication on how to do it.
Does anyone know how that can be done? (I'm specifically referring to the B2C version of AD.)
UPDATE
Here is a screenshot of where I am in the portal. This is just after I clicked the link "The domain name I need isn't shown here"
The screenshot you shared seems to be a description of Azure AD only (not Azure AD B2C).
Currently this feature is on the roadmap. Verifying your domain in the Domains tab in the Azure portal does not accomplish your goal.
See details from Azure AD B2C: FAQ.

Not able Add the B2B invitation in Azure new portal

Currently we are working on Azure SSO migration project and doing most of the task using old azure site. we have received a mail from the Microsoft via Client to use the new azure portal.
To provide the access for B2B, in old portal we straight uploaded the files with application id and the group id and that worked well.
But, in new portal when the did the same, the ids' are getting created in azure AD portal but they are not mapped in the groups that we have created for B2B invitation for the application.
Is there any approach is there. please help.
Regards,
Avisekh
The feature in the Azure Portal allows you to add individual requests by adding guest accounts, but if you need to invite multiple people or have any type of automation, you should:
Use PowerShell New-AzureADMSInvitation cmdlet
[or]
Use the Microsoft Graph API invitations
If you need to add users to groups, then you can also use the Dynamic Groups feature in Azure B2B (perhaps this is more similar to what you used to have), as well as Graph API Groups API or via PowerShell.

Azure cloud service deployment issue with pay as you go subscription - cloud services are not available in this subscription

I am having an issue while deploying an Azure web role to a cloud service. It shows me the error
Cloud services are not available in this subscription.
I am using a pay as you go subscription on Azure. I don't know if there is any limitation with this subscription for cloud service deployment or not.
.
Updated version of JerryGoyal's solution.
Cloud Service Management will have to be done using the new Azure Portal, because Cloud Service Management in the old portal will be disabled as of 11/15/2017.
Log into the new Azure Portal.
Go to the Subscriptions View.
Set your account as a Co-Admin. Microsoft Documentation.
I think the issue you're running into is that the Cloud Service Publish Wizard in VS only supports subscriptions in which you are an admin or co-admin granted via via the old portal (manage.windowsazure.com). If you've been given access via RBAC or the new portal, then VS will not see the resources under those subscriptions.
To work around it, you can build the package using msbuild.exe and then upload it via the portal.
That help?
Cloud services are not available in this subscription
The error is caused because the Cloud Services still use the old deployment model that is based on Azure Service Management (ASM).
To deploy an ASM based component to Azure you need to be ‘co-admin’ for the subscription.
Right now you are ‘Owner’ on the new portal but this role only has impact on the new ARM based resources.
So, just ask your subscription admin to login to the old portal (https://manage.windowsazure.com) and make you co-administrator:
Login to the old portal
Click on Settings –> Administrators
Click on the Add button at the bottom
Enter the co-admin email address and click on the OK button.
After this reload your Visual Studio and the problem will be solved.

Resources