TEAM,
PFA NOI INDEX 2 FOR CASE CLOSURE
Aradhana Rai
NOI Coordinator | One Legal +91 8888706969
earlier mails quoted below
On Thu, 24 Sept 2026 at 14:35, NOI ICICIHFC < icicihfcnoi@ezdocs.co.in > wrote:

TEAM

PFA DOWNLOADED E FILING FOR YOUR REFERENCE

Aradhana Rai
NOI Coordinator | One Legal  +91 8888706969

On Thu, 24 Sept 2026 at 13:32, Bholanath Yadav  /DIST/ICICIHFC/ < bholanath.yadav@icicihfc.com > wrote:

Get
Outlook for Android

From:  NOI ICICIHFC < icicihfcnoi@ezdocs.co.in >

Sent:  Thursday, 24 September 2026 13:26:58

To:  Bholanath Yadav /DIST/ICICIHFC/ < bholanath.yadav@icicihfc.com >

Cc:  Parshuram Kandurakar /EXT/OPER/ICICIHFC/ICICIHFC TOWER < parshuram.kandurakar@ext.icicihfc.com >; Vijay Wahul / /ICICIHFC/ICICIHFC TOWER < vijay.wahul@icicihfc.com >; Yogesh Sonavane /DISTP/ICICIHFC/MUM < yogesh.sonavane@icicihfc.com >; Suyog Mandve /DISTP/ICICIHFC/
< suyog.mandve@icicihfc.com >; Shubham Ayare /DISTP/ICICIHFC/ < shubham.ayare@icicihfc.com >; Drashati Limbachiya /DISTP/ICICIHFC/MUM < drashati.limbachiya@icicihfc.com >; Ankit Upadhyay /DIST/ICICIHFC/ < ankit.upadhyay@icicihfc.com >; Khushi Singh /DIST/ICICIHFC/
< khushi.singh@icicihfc.com >; Kanchan Singh /DIST/ICICIHFC/ < kanchan.singh@icicihfc.com >; Vishal Thakur /DISTP/ICICIHFC/ < vishal.thakur@icicihfc.com >

Subject:  Re: Request for NOI process in Case of Devanand Tukaram Yadav App id-77000289764

CAUTION:  External Email Warning - Do not click on any attachment or links/URL in this email unless sender is reliable.

DEAR TEAM,

PLS SHARED SANCTION LETTER FOR NOI FILING

Aradhana Rai

NOI Coordinator | One Legal
+91 8888706969

On Thu, 24 Sept 2026 at 12:50, Bholanath Yadav /DIST/ICICIHFC/ < bholanath.yadav@icicihfc.com > wrote:

Regards,

Bholanath Yadav

Senior R  elationship
Manager

9768583944

bholanath.yadav@icicihfc.com

www.icicihfc.com

1800267 3414

From:  NOI ICICIHFC < icicihfcnoi@ezdocs.co.in >

Sent:  Thursday, September 24, 2026 12:38 PM

To:  Bholanath Yadav /DIST/ICICIHFC/ < bholanath.yadav@icicihfc.com >

Cc:  Parshuram Kandurakar /EXT/OPER/ICICIHFC/ICICIHFC TOWER < parshuram.kandurakar@ext.icicihfc.com >; Vijay Wahul / /ICICIHFC/ICICIHFC TOWER < vijay.wahul@icicihfc.com >;
Yogesh Sonavane /DISTP/ICICIHFC/MUM < yogesh.sonavane@icicihfc.com >; Suyog Mandve /DISTP/ICICIHFC/ < suyog.mandve@icicihfc.com >;
Shubham Ayare /DISTP/ICICIHFC/ < shubham.ayare@icicihfc.com >; Drashati Limbachiya /DISTP/ICICIHFC/MUM < drashati.limbachiya@icicihfc.com >;
Ankit Upadhyay /DIST/ICICIHFC/ < ankit.upadhyay@icicihfc.com >; Khushi Singh /DIST/ICICIHFC/ < khushi.singh@icicihfc.com >; Kanchan
Singh /DIST/ICICIHFC/ < kanchan.singh@icicihfc.com >; Vishal Thakur /DISTP/ICICIHFC/ < vishal.thakur@icicihfc.com >

Subject:  Re: Request for NOI process in Case of Devanand Tukaram Yadav App id-77000289764

CAUTION:  External Email Warning - Do not click on any attachment or links/URL in this email unless sender is reliable.

Team

kindly share kyc document and tecnical report for NOI Proces

Aradhana Rai

NOI Coordinator | One Legal
+91 8888706969

On Wed, 23 Sept 2026 at 21:28, Bholanath Yadav /DIST/ICICIHFC/ < bholanath.yadav@icicihfc.com > wrote:

Dear Team,

Please find attached all the required documents for the NOI process for your reference.

Kindly let us know if any additional documents or information are required from our end.

Thanks & Regards,

Bholanath Yadav

SRM

Malad Branch
Your message to  ankit.upadhyay@icicihfc.com  couldn't be delivered.

ankit.upadhyay  wasn't found at  icicihfc.com .

icicihfcnoi

Office 365

ankit.upadhyay

Action Required

Recipient

Unknown To address

How to Fix It

The address may be misspelled or may not exist. Try one or more of the following:

• Send the message again following these steps: In Outlook, open this non-delivery report (NDR) and choose  Send Again  from the Report ribbon. In Outlook on the web, select this NDR, then select the link " To send this message again, click here. " Then delete and retype the entire recipient address. If prompted with an Auto-Complete List suggestion don't select it. After typing the complete address, click  Send .

• Contact the recipient (by phone, for example) to check that the address exists and is correct.

• The recipient may have set up email forwarding to an incorrect address. Ask them to check that any forwarding they've set up is working correctly.

• Clear the recipient Auto-Complete List in Outlook or Outlook on the web by following the steps in this article:  Fix email delivery issues for error code 5.1.10 in Office 365 , and then send the message again. Retype the entire recipient address before selecting  Send .

If the problem continues, forward this message to your email admin. If you're an email admin, refer to the  More Info for Email Admins  section below.

Was this helpful?  Send feedback to Microsoft .

More Info for Email Admins

Status code: 550 5.1.10

This error occurs because the sender sent a message to an email address hosted by Office 365 but the address is incorrect or doesn't exist at the destination domain. The error is reported by the recipient domain's email server, but most often it must be fixed by the person who sent the message. If the steps in the  How to Fix It  section above don't fix the problem, and you're the email admin for the recipient, try one or more of the following:

The email address exists and is correct  - Confirm that the recipient address exists, is correct, and is accepting messages.

Synchronize your directories  - If you have a hybrid environment and are using directory synchronization make sure the recipient's email address is synced correctly in both Office 365 and in your on-premises directory.

Errant forwarding rule  - Check for forwarding rules that aren't behaving as expected. Forwarding can be set up by an admin via mail flow rules or mailbox forwarding address settings, or by the recipient via the Inbox Rules feature.

Recipient has a valid license  - Make sure the recipient has an Office 365 license assigned to them. The recipient's email admin can use the Office 365 admin center to assign a lice
Keys
