Jake Thomas

My feedback

  1. 23 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Storage » Files  ·  Flag idea as inappropriate…  ·  Admin →
    Jake Thomas supported this idea  · 
  2. 27 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Storage » Files  ·  Flag idea as inappropriate…  ·  Admin →

    Hi folks,

    I have this update marked as “started” as we have 100 TiB available through premium and through limited regions for standard (see public announcement of this coming soon – should already be available).

    For File Sync, we test with number of items (files/directories), as we don’t really care about file share size (it doesn’t affect the performance of sync – just upload/download). With v7, our current tested threshold (not a hard limit) is 50 million objects. This was done on ~20 TiB shares, but you should be able to go larger without issue.

    We plan to continue to scale up this tested threshold with future versions of the agent as we continue to test.

    Thanks,

    Will Gries
    Program Manager, Azure Files

    Jake Thomas supported this idea  · 
  3. 44 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Storage » Files  ·  Flag idea as inappropriate…  ·  Admin →
    Jake Thomas supported this idea  · 
  4. 191 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Storage » Files  ·  Flag idea as inappropriate…  ·  Admin →
    Jake Thomas supported this idea  · 
  5. 1,065 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    39 comments  ·  Storage » Files  ·  Flag idea as inappropriate…  ·  Admin →
    Jake Thomas supported this idea  · 
  6. 1,528 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    90 comments  ·  Storage » Files  ·  Flag idea as inappropriate…  ·  Admin →

    As you mentioned, we initiate a change detection job once every 24 hours to enumerate the Azure file share and scan for changes. This is required for the Azure file share because Azure Files currently lacks a change notification mechanism like Windows Server has. Long term we will add this capability and have automatic immediate sync.

    There is now a way to trigger sync to happen on files that are placed directly in the Azure File share. With this new cmdlet you can point sync to particular files or directories and have it look for changes right then. This is intended for scenarios where some type of automated process in Azure is doing the file edits or migrations are done by an admin (like moving a new directory of files into the share). For end-user changes, the best thing to do is install Azure File Sync in an IaaS VM…

    Jake Thomas supported this idea  · 
  7. 223 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    started  ·  12 comments  ·  Storage » Files  ·  Flag idea as inappropriate…  ·  Admin →
    Jake Thomas commented  · 

    @Microsoft Azure Storage Team.
    We migrated to Azure File Sync, and now really have a problem on our hands with the 5TiB limitation. Is there any update on when this will be upped to 100TiB?

    Jake Thomas supported this idea  · 
  8. 544 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Thank you for your feedback! The feature team is aware of this suggestion and will keep it under consideration. There are technical challenges to overcome in order to make this happen. Please keep the votes coming if this feature matters to you.

    Chen

    Jake Thomas commented  · 

    This would be amazing for our Intune deployment process.

    Here's an example:
    80% of users in our organization get Office 365 with all core apps except Access, Groove, and Publisher. We deploy this to them based on whether or not they have an Office E3 license.
    An additional 5% of our users have Project or Visio. Being licensed could put them in a group to get Visio or Project automatically assigned and deployed.

    Jake Thomas supported this idea  · 

Feedback and Knowledge Base