Refine OAuth identity passthrough instructions by removing optional steps for client secret management and clarifying scope creation process

Author: ggailey777

articles/azure-functions/functions-mcp-foundry-tools.md

@@ -135,10 +135,11 @@ For a Functions-hosted MCP server with built-in authentication, use custom OAuth
 
     Replace `<TENANT_ID>` with your actual tenant ID value.
 
-1. (Optional) If your app requires a client secret, select **Manage** > **Certificates & secrets**, and then create or copy an existing client secret value.
-
-1. (Optional) Select **Manage** > **Expose an API** and create or copy an existing scope.  
+1. Select **Manage** > **Expose an API** and create or copy an existing scope.  
 
+<!---Seems like we don't need this...
+1. (Optional) If your app requires a client secret, select **Manage** > **Certificates & secrets**, and then create or copy an existing client secret value.
+-->
 After you configure OAuth identity passthrough in the Foundry portal, you receive a redirect URL. You must return to this Entra app registration to add this redirect URL to your Microsoft Entra app registration.
 
 ### [Unauthenticated](#tab/unauthenticated)