Currently we have an ASP.NET website hosted on IIS 7 . We use an user account (created on Active Directory) as Identity for APP pool . Website is accessed by both internet and intranet users. Till now the user account which is being used as identity in APP pool has internet access but in coming days this user account will not have internet access ( Internet access will be blocked for this user account as per organization policy) .Can some body let me know whether this will affect the website in any way? Will the external users still be able to access the site if we continue to use the same user account as identity ?
If we're going to say "no, that'll work just fine" and it doesn't, who are you going to blame? It is your responsibility to test this with a machine and a user that don't affect your production environment.
However, no, your application pool identity generally doesn't need internet access. The only reason to need internet access for your application pool identity, is when one application running on that pool needs internet access. For example API calls, downloading images, or whatever.