Triggering pipeline and triggered pipeline
Pipeline completion trigger is defined in the pipeline definition of triggered pipeline.
My Playground
Pipeline completion trigger is defined in the pipeline definition of triggered pipeline.
There are already tons of good articles talking about benefit of using the httpClientFactory from .net core 2.1.
There is always time we may find it useful not to use the default token life time provided by Microsoft Identity Platform, e.g.: we may want to shorten the token exirty time, in order to test scenario where application is capable of ‘refreshing’ the access token when the original one expires.
Microsoft has hence introduced a way to allow you to configure the token lifetimes, this configuration is per tenant, service principal, or application.
In preview only, so need to load the module before using it. Below is an example to demo how a policy could be created and assigned to a service principal.
Working on a recent project I’ve decided to script the registration of Azure Applications, as I’m not dealing with one application, not five, not ten, but almost a dozen of Azure Applicatoins with almost the same configurations.
AAD refers to v1 endpoint, while MIP refers to v2 endpoint.
AAD and MIP exist side by side, for each tenant, you’ll have one discovery endpoint for each of them, e.g.:
I ran into a weird problem this week. Long story short: Pure code changes in startup Project 1), without touching the project reference/or binding redirect at all, ended up a completely different start-up project 2) gets crashed following my changes: