ACTIVE DIRECTORY, EXCHANGE, office 365, citrix

First I would never recommend an older ver than the current version when upgrading also you probably cannot get office 2013 if you are using O365.

You do not need ADFS unless you are looking Single Sign-on.

Azure AD Sync will sync your AD ON-premise with O365. https://docs.microsoft.com/en-us/azure/active-directory/connect/active-directory-aadconnect

Is this xenapp or xendesktop (vdi).

we use citrix receiver to connect  it is xendesktop i believe

i need to know how we can upgrade to outlook 2016 , u mean to say outlook 2013 wont work with office 365?

if we use AAD sync , are not the users in azure ACTIVE DIRECTORY cant we edit the attributes  from there directly or on premise AD has to be removed?

The purpose of ADD sync is to keep all your Users info from the on-premise to sync with azure AD/O365.

So yes to your question if I read it correctly.

You can easily test this.
This for the older version, but should help you.

https://blogs.technet.microsoft.com/nawar/2016/02/25/forcing-synchronization-with-azure-ad-connect-1-1-aad-connect-1-1/

sir, what i am asking is can you give clear answer

1) if we are syncing through AAD sync from on premise to cloud, are noot the users in azure AD already, cant we edit the attributes there in azure AD  in office 365 ?? or we have to remove on premise AD environment

2) are any steps required to upgrade outlook 2010 to outlook 2016 in citrix environment i need to do for 300 users.

3) when outlook 2010 is compatible with office 365, why outlook 2013 not? as you pointed above

1) if we are syncing through AAD sync from on premise to cloud, are noot the users in azure AD already, cant we edit the attributes there in azure AD  in office 365 ?? or we have to remove on premise AD environment

I cannot confirm your question at this time, but I will try and find an answer.

2) are any steps required to upgrade outlook 2010 to outlook 2016 in citrix environment i need to do for 300 users.

I asked a question earlier if your Outlook on XenApp or Xendesktop.  Once this is confirmed I can give yo a better answer

3) when outlook 2010 is compatible with office 365, why outlook 2013 not? as you pointed above

If you are using O365 then you do not even have a choice of Outlook 2013.  There only is the most current branch available for O365

There only is the most current branch available for O365- what is the meaning of this statement, didnt get you

we have xendesktop where outlook 2010 is configured on workstations in office.

2)) we recently faced a soft delete mailbox in office 365, that was due to the user AD account was disabled in on premise so we had to reenable the AD account and resync through AAD
sync in order to get the mailbox out from soft delete

so my question here is the user account was not in azure active directory then and only in on premise AD ,

had the user been in azure active directory and not on on premise and the mailbox could still go to soft delete?

1)Is your Xendesktop a Persistent or a Non-Persistent disk?

So you will need to create a new version of your vdisk | Update the application/applications you wish | Promote it to a test mode and start a few VM up with the new disk | Once yo feel its right you then promote to production.  Once at Production stage any new vms that start up they will be using the newest version of the disk.  

What do you mean by persistent or non -persistent disk?-just short answer would satisfy- so you mean to say i cant directly upgrade outlook 2010 itself , i need to have a new version of vdisk and install outlook 2016 afresh if yes then leave outlook 2010 untouched as it is??

2) I see what you are saying now regarding Azure AD.  If you have a Hybrid environment, which you do it would not make any sense to not sync your on-premise with Azure.  I am assuming that your Exchange is in Azure and not on-premise.  I know you can create users in O365 that do not exist in your on-premise.  So if this account has a mailbox you should not experience a soft delete.  I have a few accounts in O365 (not Azure AD) and they do not replicate back to my system.

yes exchange is in azure but AD is not, what my question was if we are syncing users from on premise AD to azure AD are we not creating user accounts in AZURE AD. had there been no on premise AD and user account only in azure AD , can there bea possibility of soft delete of mailbox if yes then how can we restore it?

got it we have presistent desktops, also kindly answer my above question. thanks for your time in clearing my doubt

Would you be able to bullet point your entire Citrix infrastructure?  I am taking assumptions about your environment and I want to give you the right info.

we have full felged citrix environment , wont i be upgrading outlook 2016 in citrix studio

That is what I am asking. My citrix environment maybe different.  I want have an understanding of it.
Mine consist of the following parts:

• NetScaler
• StoreFront
• Desktop Delivery Controllers
• Provision Server
• XenServers for my hypervisors.
• my VDI environment is a single Non-Persistent Disk (Read Only) for all users. All machines that spin up are using that read-only disk.

When I patch or update my Non-Persistent disk I use Provisioning Server to version the non-Persistent disk to a maintenance mode (read-write mode).  When I am happy with the build I then promote it to Test and then Production.
https://stealthpuppy.com/persistent-v-non-persistent/#.WxQm1ExFzoo

Defining Terms
Let me first list the various terms that you might hear when discussing this topic:
Persistent, stateful, full clone – a Windows instance is persistent because we want to protect that Windows install. Rebuilding it from scratch can take time and effort. A physical PC or server is persistent because there’s no abstraction of the OS from the hardware.
Non-persistent, stateless, pooled, shared, linked-clone – a non-persistent virtual desktop is often destroyed at user logoff, reboot or shutdown. A Remote Desktop Services (RDS) environment can also be considered non-persistent, even though the underlying Windows instance may be persistent.
So many words to describe essentially the same thing. For clarity’s sake, let’s stick with persistent and non-persistent for the rest of this article.

W