@types/office-js-preview 1.0.582 → 1.0.584

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. office-js-preview/README.md +1 -1
  2. office-js-preview/index.d.ts +15 -58
  3. office-js-preview/package.json +2 -2
office-js-preview/README.md CHANGED
@@ -8,7 +8,7 @@ This package contains type definitions for office-js-preview (https://github.com
8
8
  Files were exported from https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/office-js-preview.
9
9
 
10
10
  ### Additional Details
11
- * Last updated: Mon, 14 Apr 2025 22:37:06 GMT
11
+ * Last updated: Sat, 19 Apr 2025 18:36:48 GMT
12
12
  * Dependencies: none
13
13
 
14
14
  # Credits
office-js-preview/index.d.ts CHANGED
@@ -15689,14 +15689,6 @@ declare namespace Office {
15689
15689
  * <td>New messages and message replies</td>
15690
15690
  * </tr>
15691
15691
  * <tr>
15692
- * <td>IPM.Note.SMIME</td>
15693
- * <td>Encrypted messages that can also be signed</td>
15694
- * </tr>
15695
- * <tr>
15696
- * <td>IPM.Note.SMIME.MultipartSigned</td>
15697
- * <td>Clear-signed messages</td>
15698
- * </tr>
15699
- * <tr>
15700
15692
  * <td>IPM.Schedule.Meeting.Request</td>
15701
15693
  * <td>Meeting requests</td>
15702
15694
  * </tr>
@@ -15748,14 +15740,6 @@ declare namespace Office {
15748
15740
  * <td>New messages and message replies</td>
15749
15741
  * </tr>
15750
15742
  * <tr>
15751
- * <td>IPM.Note.SMIME</td>
15752
- * <td>Encrypted messages that can also be signed</td>
15753
- * </tr>
15754
- * <tr>
15755
- * <td>IPM.Note.SMIME.MultipartSigned</td>
15756
- * <td>Clear-signed messages</td>
15757
- * </tr>
15758
- * <tr>
15759
15743
  * <td>IPM.Schedule.Meeting.Request</td>
15760
15744
  * <td>Meeting requests</td>
15761
15745
  * </tr>
@@ -16307,14 +16291,6 @@ declare namespace Office {
16307
16291
  * <td>New messages and message replies</td>
16308
16292
  * </tr>
16309
16293
  * <tr>
16310
- * <td>IPM.Note.SMIME</td>
16311
- * <td>Encrypted messages that can also be signed</td>
16312
- * </tr>
16313
- * <tr>
16314
- * <td>IPM.Note.SMIME.MultipartSigned</td>
16315
- * <td>Clear-signed messages</td>
16316
- * </tr>
16317
- * <tr>
16318
16294
  * <td>IPM.Schedule.Meeting.Request</td>
16319
16295
  * <td>Meeting requests</td>
16320
16296
  * </tr>
@@ -17397,8 +17373,9 @@ declare namespace Office {
17397
17373
  *
17398
17374
  * **Important**:
17399
17375
  *
17400
- * - In February 2025, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and
17401
- * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} tokens will be turned off by default for all Exchange Online tenants.
17376
+ * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and
17377
+ * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} tokens have been turned off by default for most Exchange Online tenants.
17378
+ * Administrators can reenable legacy tokens for tenants and add-ins until June 2025. In October 2025, legacy tokens will be completely turned off for all tenants.
17402
17379
  * This is part of {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative},
17403
17380
  * which gives organizations the tools needed to respond to the current threat landscape. Exchange user identity tokens will still work for Exchange on-premises.
17404
17381
  * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}.
@@ -17916,8 +17893,9 @@ declare namespace Office {
17916
17893
  *
17917
17894
  * **Important**:
17918
17895
  *
17919
- * - In February 2025, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and
17920
- * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} tokens will be turned off by default for all Exchange Online tenants.
17896
+ * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and
17897
+ * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} tokens have been turned off by default for most Exchange Online tenants.
17898
+ * Administrators can reenable legacy tokens for tenants and add-ins until June 2025. In October 2025, legacy tokens will be completely turned off for all tenants.
17921
17899
  * This is part of {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative},
17922
17900
  * which gives organizations the tools needed to respond to the current threat landscape. Exchange user identity tokens will still work for Exchange on-premises.
17923
17901
  * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}.
@@ -18020,8 +17998,9 @@ declare namespace Office {
18020
17998
  *
18021
17999
  * **Important**:
18022
18000
  *
18023
- * - In February 2025, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and
18024
- * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} tokens will be turned off by default for all Exchange Online tenants.
18001
+ * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and
18002
+ * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} tokens have been turned off by default for most Exchange Online tenants.
18003
+ * Administrators can reenable legacy tokens for tenants and add-ins until June 2025. In October 2025, legacy tokens will be completely turned off for all tenants.
18025
18004
  * This is part of {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative},
18026
18005
  * which gives organizations the tools needed to respond to the current threat landscape. Exchange user identity tokens will still work for Exchange on-premises.
18027
18006
  * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}.
@@ -18194,8 +18173,9 @@ declare namespace Office {
18194
18173
  *
18195
18174
  * **Important**:
18196
18175
  *
18197
- * - In February 2025, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and
18198
- * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} tokens will be turned off by default for all Exchange Online tenants.
18176
+ * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and
18177
+ * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} tokens have been turned off by default for most Exchange Online tenants.
18178
+ * Administrators can reenable legacy tokens for tenants and add-ins until June 2025. In October 2025, legacy tokens will be completely turned off for all tenants.
18199
18179
  * This is part of {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative},
18200
18180
  * which gives organizations the tools needed to respond to the current threat landscape. Exchange user identity tokens will still work for Exchange on-premises.
18201
18181
  * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}.
@@ -18309,8 +18289,9 @@ declare namespace Office {
18309
18289
  *
18310
18290
  * **Important**:
18311
18291
  *
18312
- * - In February 2025, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and
18313
- * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} tokens will be turned off by default for all Exchange Online tenants.
18292
+ * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and
18293
+ * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} tokens have been turned off by default for most Exchange Online tenants.
18294
+ * Administrators can reenable legacy tokens for tenants and add-ins until June 2025. In October 2025, legacy tokens will be completely turned off for all tenants.
18314
18295
  * This is part of {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative},
18315
18296
  * which gives organizations the tools needed to respond to the current threat landscape. Exchange user identity tokens will still work for Exchange on-premises.
18316
18297
  * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}.
@@ -19618,14 +19599,6 @@ declare namespace Office {
19618
19599
  * <td>New messages and message replies</td>
19619
19600
  * </tr>
19620
19601
  * <tr>
19621
- * <td>IPM.Note.SMIME</td>
19622
- * <td>Encrypted messages that can also be signed</td>
19623
- * </tr>
19624
- * <tr>
19625
- * <td>IPM.Note.SMIME.MultipartSigned</td>
19626
- * <td>Clear-signed messages</td>
19627
- * </tr>
19628
- * <tr>
19629
19602
  * <td>IPM.Schedule.Meeting.Request</td>
19630
19603
  * <td>Meeting requests</td>
19631
19604
  * </tr>
@@ -19677,14 +19650,6 @@ declare namespace Office {
19677
19650
  * <td>New messages and message replies</td>
19678
19651
  * </tr>
19679
19652
  * <tr>
19680
- * <td>IPM.Note.SMIME</td>
19681
- * <td>Encrypted messages that can also be signed</td>
19682
- * </tr>
19683
- * <tr>
19684
- * <td>IPM.Note.SMIME.MultipartSigned</td>
19685
- * <td>Clear-signed messages</td>
19686
- * </tr>
19687
- * <tr>
19688
19653
  * <td>IPM.Schedule.Meeting.Request</td>
19689
19654
  * <td>Meeting requests</td>
19690
19655
  * </tr>
@@ -20499,14 +20464,6 @@ declare namespace Office {
20499
20464
  * <td>New messages and message replies</td>
20500
20465
  * </tr>
20501
20466
  * <tr>
20502
- * <td>IPM.Note.SMIME</td>
20503
- * <td>Encrypted messages that can also be signed</td>
20504
- * </tr>
20505
- * <tr>
20506
- * <td>IPM.Note.SMIME.MultipartSigned</td>
20507
- * <td>Clear-signed messages</td>
20508
- * </tr>
20509
- * <tr>
20510
20467
  * <td>IPM.Schedule.Meeting.Request</td>
20511
20468
  * <td>Meeting requests</td>
20512
20469
  * </tr>
office-js-preview/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@types/office-js-preview",
3
- "version": "1.0.582",
3
+ "version": "1.0.584",
4
4
  "description": "TypeScript definitions for office-js-preview",
5
5
  "homepage": "https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/office-js-preview",
6
6
  "license": "MIT",
@@ -46,7 +46,7 @@
46
46
  "scripts": {},
47
47
  "dependencies": {},
48
48
  "peerDependencies": {},
49
- "typesPublisherContentHash": "4bb42c12e78e634d453cde7b00437bff3803a0ad5ee4f2fd9923bf869cad8cfe",
49
+ "typesPublisherContentHash": "d22d8ecbe25f0ee7198a62e2f14ebf08f26308b05bce03e04b7006d5e6c3288b",
50
50
  "typeScriptVersion": "5.1",
51
51
  "nonNpm": true
52
52
  }