Update use-aadhttpclient-enterpriseapi-multitenant.md

removed the fact that "resource" property also supports ID look up. This is in response of the following gitHub issue: SharePoint#8501

Author: lucabandMSFT

docs/spfx/use-aadhttpclient-enterpriseapi-multitenant.md

@@ -308,7 +308,7 @@ To the **solution** property, add a new section named `webApiPermissionRequests`
 }
 ```
 
-The value of the **resource** property refers to either the name or the ID of the Azure AD application used to secure the API. Using the name is more readable and easier to maintain over time. The value of the **scope** property specifies the permission scope that your solution needs to communicate with the API. In this tutorial, Azure AD is used only to secure the API, so `user_impersonation` is the scope that you'll use.
+The value of the **resource** property refers only to the name of the Azure AD application used to secure the API. The value of the **scope** property specifies the permission scope that your solution needs to communicate with the API. In this tutorial, Azure AD is used only to secure the API, so `user_impersonation` is the scope that you'll use.
 
 > [!NOTE]
 > If you want to connect to an enterprise API that has been created previously, contact your administrator to provide you with details for the Azure AD application used to secure it. You'll need information such as the application ID, permissions the application exposes and the audience it's configured to.