Whenever I make a change to my Azure AAD B2C policy, either a basic one from the Azure portal or a custom policy, I did not seem to observe the change immediately when running it through my web application or mobile application. It usually takes a few minutes before the change takes effect. This is quite inconvenient for me to test my web application as well as my mobile application.
Azure Active Directory B2C uses cache to improve the performance of your Production traffic. As a side effect, the change to your policy won't take effect immediately as the service may still keep an old copy of your policy file. This usually takes 1-2 minutes.
However, the cache will be disabled if you run your user journey through the "Run Now" button in the Azure B2C portal blade. We recommend testing your policy through that "Run Now" button so you will observe the change to your policy file immediately.
Related
I have a Asp.Net Core Razor Pages web app that has some pages Azure AD authenticated and some unauthenticated/anonymous. It works perfectly when I run in the debug mode in Visual Studio. When I publish the same on the Azure Web App I can either make the entire web app Authenticated or Unauthenticated. Is there a way to allow both at the same time?
From the azure portal, we can see that azure webapp does not support simultaneous settings. But we can set it from the code, and Noah Stahl and Tiny Wang are correct.
Phenomenon:
Create a simple application that does not include login, or simply put an index.html file, we can set it on the portal to perform the third-party login function.
As you can see, you can only choose one, Authenticated or Unauthenticated. And if you choose Authenticated, you can also choose one of the providers. This function is the simplest function in the portal.
Suggestion:
If you want to achieve multiple third-party logins, you still need to start from the code level so that you don't need to set up on the portal. It should be too simple on the portal.
You can refer below official doc:
Facebook, Google, and external provider authentication in ASP.NET Core
When you implement it, you can still access other resources in the unlogged state. When you need to log in, all supported third-party buttons will appear on the login page. Click the button to log in.
The option setting in the portal is a restriction on the current global access to the entire website.
Even if always on flas is setted, azure closes our web apps after inactivity 20 minutes. Then it opens them when first request comes. Is it possible to avoid from this behaviour. We want our services always running and responds immediately.
App service plan is Standard: 1 Large. Subscription's offer is "Azure in Open"
Thanks in advance
Go to the App Service Web App within the Azure Portal, navigate to the "Application Settings" section, and set the "Always On" option to "On". This will ensure the application is always running.
FYI, the "Application Settings" pane in the Azure Portal is changing to "Configuration", and is currently in Preview at the time of writing this.
In the past there was both the separate website AND the Azure classic portal for managing Signin Apps. In the Classic portal it would give you the ability to edit the ReplyUrls.
In the new portal no matter how you create an app (Enterprise or Application Registration) you can't edit your ReplyUrls from the UI. (With Application you can set them the first time but then they don't show up in the Application list from then on so it's impossible to edit them)
Meanwhile these same apps can have their replyUrls updated using Powershell without any problem.
To me this is a blocker bug, but maybe I'm doing something wrong? I've successfully gotten only 1 application to show up under application registrations. All others including ones created back in the Azure Classic day show up in Enterprise applications without even the Sign On Option showing up in the list of options for the application per the instructions on Microsoft's website.
I can private message an app Id as an example.
The user experience of the Azure portal changed for the worse (in my opinion).
I also had trouble finding my old apps... turns out they are now "hidden" by default.
they don't show up in the Application list from then on so it's impossible to edit them)
You will find them under "all apps".
I am hosting web application in azure active directory.
I want to enable an option called as “External Access” after clicking on the applications button.
Now, the issue is when I click on “Add app” , I am not getting the option to select “Single sign on,read directory data”( I have added the screen shot below) , so eventually the “External Access” is not getting enabled in the applications tab.
Any solution for this?
Guess currently this option is renamed to Application is MultiTenant and you have to set this option for external access in the respective application's configure section.
"External access" means that it is a multi-tenant application, where you expect to have more than one organization (or at least more than one directory) consuming the application. As #Bamura mentions, this was renamed in the Azure portal to "application is multi-tenant".
"Single sign-on", "read-only", etc. are permissions that an application has to a resource. One of these resources is Azure AD itself (via the Graph API), but it isn't the only one. For example, you can have one application representing a web API, and another application representing native client apps that access the web API.
You can control which permissions an app has under the "Permissions to other applications" section at the bottom of the 'Configure' screen. You'll notice the default is single sign-on delegated permission (i.e. as a user).
I have an issue that when I deploy a simple web application with startup tasks. After deploying, when I will click on the instance, then it seems to be disabled, as shown in the image below:
Is there any specific reason for this? And how can I overcome this situation?
This whole section is all about Remote Desktop connectivity. Not the "Azure Connect". So far I have never seen the "Connect" icon disabled after successfull deployment. If you are experiencing issues make sure:
You have enabled remote desktop prior you deploy (once configured it
stays configured, unless you explicitly disable it)
Your account expiration date has not passed
Your instance is in "Ready" state
The certificate used for password encryption has not expired
Wait a couple of minutes after instance state is "Ready" - there
might be a slight delay between RDP configuration and actual
enablement
If you still have issues, try clicking on a Role, not an instance. Then the other 2 options shall be enabled (Enable & Configure). Check their status and change it, if the "Enable" checkbox is not checked. And check the "Configure" for the user account and password.