fixing readme for Isolated

artmasa · web-flow · commit 16104e281e2b · 2024-03-13T17:39:34.000-05:00
diff --git a/src/isolated/README.md b/src/isolated/README.md
@@ -27,7 +27,7 @@ var host = new HostBuilder()
     .ConfigureServices(services =>
     {
         services
-            .AddFunctionsAuthorization()
+            .AddFunctionsAuthenticationation(JwtBearerDefaults.AuthenticationScheme)
             .AddJwtBearer(options =>
             {
                 options.Authority = "https://login.microsoftonline.com/your-tenant-id";
@@ -77,4 +77,4 @@ public class Functions
 ```
 
 Something really nice to notice is that for Functions in Isolated mode, the `HttpTriggerAttribute` default `AuthenticationLevel` is `Anonymous`, playing really well with the attribute.<br/>
-Also notice how the second function uses the `AuthorizeAttribute` attribute to apply a policy to the function. `FunctionAuthorizeAttribute` was left as part of the framework only to make it easier to migrate from In-Proc to Isolated, but they can be used interchangeably.
+Also notice how the second function uses the `AuthorizeAttribute` attribute to apply a policy to the function. `FunctionAuthorizeAttribute` was left as part of the framework only to make it easier to migrate from In-Proc to Isolated, but they can be used interchangeably.

Original file line number	Diff line number	Diff line change
`@@ -27,7 +27,7 @@ var host = new HostBuilder()`
`27`	`27`	`.ConfigureServices(services =>`
`28`	`28`	`{`
`29`	`29`	`services`
`30`		`- .AddFunctionsAuthorization()`
	`30`	`+ .AddFunctionsAuthenticationation(JwtBearerDefaults.AuthenticationScheme)`
`31`	`31`	`.AddJwtBearer(options =>`
`32`	`32`	`{`
`33`	`33`	`options.Authority = "https://login.microsoftonline.com/your-tenant-id";`
`@@ -77,4 +77,4 @@ public class Functions`
`77`	`77`	```
`78`	`78`
`79`	`79`	Something really nice to notice is that for Functions in Isolated mode, the `HttpTriggerAttribute` default `AuthenticationLevel` is `Anonymous`, playing really well with the attribute.<br/>
`80`		-Also notice how the second function uses the `AuthorizeAttribute` attribute to apply a policy to the function. `FunctionAuthorizeAttribute` was left as part of the framework only to make it easier to migrate from In-Proc to Isolated, but they can be used interchangeably.
	`80`	+Also notice how the second function uses the `AuthorizeAttribute` attribute to apply a policy to the function. `FunctionAuthorizeAttribute` was left as part of the framework only to make it easier to migrate from In-Proc to Isolated, but they can be used interchangeably.